Maybe the blue ray box should have an entire SSD in them or some kind of NextGen Compact flash as long as it's a standard format and not a proprietary format like a switch game. You can buy blank CDs, DVDs, SD cards and there are standards in place to make them readable by entire fleets of devices.
It's harder for games but I'm coming at this from a games preservation angle.
Games keep getting bigger and require installation to drive to effectively load assets quickly. I really envy the ability to not have to perform an installation to the device. If your game was simply its own storage device again then you could have that plug and play like experience back and also have that ~4GBps read that even the cheapest NVME drives can offer.
I have DVDs, but I also have MKV files, and I have the ability to go between these formats. I suggested something like flatpak because a universal physical media image format for games would be just one more way to easily preserve content offline indefinitely and neatly keep it pretty platform agnostic.
That was my train of thought. I know the likelihood of this being done by a real company is slim to none because of DMCA and over engineering another format is pointless if they can force everything to be download only IRL but I would like to push back and I can't easily archive all this stuff forever on an ever growing 48TB Nas on my home. I would like offline ownership and convenience please.
If it's going to be too expensive for a company to put Alan Wake Two onto physical media then I'd like a way to do it myself so it continues to work when epic decides they want to pull a Warner Bros and rip it off the internet forever and claim it was a loss to get tax breaks. It would also be cool if it didn't have to install and it just started.
I understand the difficulty involved with that but we're halfway there with software running containerized on Linux.
A man can dream.
I have tried (story option below):
Currently virtualization for the desktop, even though that is in fact the future, there are many issues at the moment. For instance, graphics are holding me back.
Wendell on level 1 techs has plenty of these videos and there is one specifically where he goes in depth on spinning up a windows virtual machine and essentially using a GitHub project to make registry hacks to turn that windows VM into a fake RDS app server then using those apps via the RDP protocol.
I really like this solution but it is still less than desirable when attempting to save files, pass through devices to apps other than keyboard and mouse, run corporate ssl VPN Clients (they often enforce desktop sessions non-rdp via policy).
I follow these threads closely: https://forum.level1techs.com/t/vfio-passthrough-in-2023-call-to-arms/199671
I sometimes think maybe moving to an Intel processor with onboard video for my displays and then using the Nvidia driver patch like this https://github.com/DualCoder/vgpu_unlock or this https://github.com/ProTechEx/vgpu-proxmox to drive local 3D apps and pass GPUs into VMs is potentially something that can be used to get this going (without the need for a second discreet GPU).
I just don't want to have to do this. So I just have a windows desktop (still).
I wear it out. Screaming, kicking, blasting "we're in this together now" by NIN cranked up to 11. Physical exhaustion will bring with it its own form of revelation.
A good workout helps.
Pakleds are an alien race from star trek. They're known for tricking smarter people into helping them only so they can take advantage of them, ensnare them, and then dominate them. They also on average have low IQ (in universe).
Are Diablo 3 server emus any good? I haven't looked in a long while but now I'm intrigued.
There are a few applications out there that I don't fully understand the deployment of but seem to work in containers.
Typically the storage is mounted outside of the container and passed through in the compose file for docker. This allows your data to be persistent. Ideally you would also want those to reside in a file system that can easily be snapshot like ZFS. When you pull down a new docker container, it should just remount the same location and begin to run.
Or at least that's how I'd imagine it would run. I feel like one would run into the same challenges people have running databases persistently in containers.
I'm also interested in these alternatives!
I'm fooling around with a few samba AD docker containers. I ask because I've phased almost everything else out of my lab environment.
💯 on point here. Everyone knows it and doesn't understand why.
https://bettermarketing.pub/the-great-marketing-deregulation-2125a0efe094
Yeah, I think as the replacement for x before Wayland?