Comment on New Steam Beta can run the Linux client inside a container with 64bit
FooBarrington@lemmy.world 3 weeks agoa very normal thing for your very functional software to have
What an incredibly weird complaint
Comment on New Steam Beta can run the Linux client inside a container with 64bit
FooBarrington@lemmy.world 3 weeks agoa very normal thing for your very functional software to have
What an incredibly weird complaint
TheTechnician27@lemmy.world 3 weeks ago
That it’s weird for Valve’s client to be running inside a container?
My other software isn’t containerized that I know of. I don’t run Firefox in Docker.
FooBarrington@lemmy.world 3 weeks ago
Why the fuck is it weird for a client to run inside a runtime environment with well-defined library versions, when that client has to ship that runtime environment anyways to ensure the games can actually run on a broad range of systems?
Oh, sure, it’s so much better if the client relies on system libraries instead. Yes please, I like incompatibilities and issues with debugging. So much better than loading a different set of libraries. Stupid Valve!
TheTechnician27@lemmy.world 3 weeks ago
Alright, let’s just say it’s perfectly fine because of the problem Valve creates by making you open Steam when you play games. It’s just 64-bit for the runtime, not even the client itself. It’s 2026. I’m not going to act like this is an accomplishment.
FooBarrington@lemmy.world 3 weeks ago
Do you even know what any of the words you’re using mean? It doesn’t matter whether the Steam client is running in the runtime, you still want the same containerization to run your games, because that’s how they make sure the games run everywhere.
You’re just angrily flinging shit around without understanding what any of this is about. Don’t you have anything better to do?
Jako302@feddit.org 3 weeks ago
You can run steam games without opening steam as long as they don’t use the steamworks DRM or require an additional login (Ubisoft, Bethesda). Both of these issues are created by the developers / publishers, not steam.
9point6@lemmy.world 3 weeks ago
Funnily enough, people running in Ubuntu do get Firefox in a container by default IIRC as it’s delivered as a snap
TheTechnician27@lemmy.world 3 weeks ago
You recall correctly. It’s another one of Canonical’s attempts to shoehorn their trash.
fruitycoder@sh.itjust.works 3 weeks ago
I run most of my software in containers. Firefox is in a flatpak. My terminal shells are all containers using distrobox. My homelab services are all containers. My few VMs (i run a few vituralized rke2 clusters, sometimes a test version of my baremetal harvester cluster, and test versions of my desktops)? Also running in containers. My desktop OSs are also containers (ublue, SteamOS, and SUSE Elemental).
The future is now old man! :p
But honestly linux namespaces and overlay filesystems are the bees knees. Create reusable layers of filesystems, use just the ones needed for a given app/service. Expose just what a service or app needs to for a given function. You end up with an extemly portable, and consistent system that has cleaner seperations of concerns. For basically free. From an app dev perspective you remove a whole matrix of supported configurations to worry about (distro/version/packages installed/etc).