Linux package managers are an abomination and a failed model. As evidenced by Docker being required both to reliable build and reliably run modern software.
glibc is an abomination of bad design ideas from the 80s. Compilers relying on whatever random ass version of a .so you have is broken AF. The fact that you can’t target an arbitrarily version of glibc or runtime environment is an embarrassment.
Once upon a time I shipped a popular-ish game with Linux support. 1% of Linux users represented 50% of bug reports. And no it’s not because Linux players were more reliable at reporting Linux issues. It has been a few years, but supporting more than SteamDeck is likely similar. At least for non-proton builds.
I like Portage when it works. When it doesn't, I don't like portage very much.
I'm not sure if you can "alternatives" glibc in Gentoo, but the "whatever .so you have" isn't a thing there, you can slot different versions if you need to.
If I want to test some software I'll use Ubuntu with docker or whatever, but to deploy to production I will make it run on Gentoo. Hell or high water.
Windows software still ships every .dll it needs, unless it is a Microsoft one. Do a search for msvc.dll or whatever sometime and marvel at the pagination.
That's not a platform issue, that's a "these companies simply don't ship Linux versions".
> Linux package managers are an abomination and a failed model.
Ironic then that some Windows tools (Chocolatey) model them and Windows has WSL because tons of devs find that model easier.
> As evidenced by Docker being required both to reliable build and reliably run modern software.
Docker doesn't do away with that model, it just allows you to isolate specific versions of libraries and tools you need in a namespace/container.
The standard model for shipping Windows software is to ship all the libraries needed with the software. Which isn't much different than what Docker is doing.
> glibc is an abomination of bad design ideas from the 80s. Compilers relying on whatever random ass version of a .so you have is broken AF. The fact that you can’t target an arbitrarily version of glibc or runtime environment is an embarrassment.
Maybe it's a bad model, can't speak to that. But you can statically link a C/C++ runtime with your software if you want, or ship alternative glibc versions.
Also, if we're talking about shipping games on Steam, you can simply target the Steam runtime. It'll work on Steam deck + any Linux system.
I am so glad that I'm not the only one thinking package managers are complete nonsense. Even on macOS I have always found Homebrew or MacPorts to be rather dumb (at least the latter is saner in some ways).
Package managers have so many fundamental problems it's hard to even get started.
But they appeal to the Linux type of person because it's a very communist type approach to things, authoritarian and panopticon like way.
At least nowadays they are trying to allow installing software in some more convenient way but I'm not holding my breath considering there are competing implementations.
Linux package managers are an abomination and a failed model. As evidenced by Docker being required both to reliable build and reliably run modern software.
glibc is an abomination of bad design ideas from the 80s. Compilers relying on whatever random ass version of a .so you have is broken AF. The fact that you can’t target an arbitrarily version of glibc or runtime environment is an embarrassment.
Once upon a time I shipped a popular-ish game with Linux support. 1% of Linux users represented 50% of bug reports. And no it’s not because Linux players were more reliable at reporting Linux issues. It has been a few years, but supporting more than SteamDeck is likely similar. At least for non-proton builds.