Installing old Linux applications IS a problem. They’re available only if someone repackaged them for newer distros. If not they can’t run anymore because of dependencies mismatch.
I’ll take a program that isn’t getting updates anymore or simply doesn’t work in my modified environment using slightly more ram and storage over it not working at all.
I have firsthand experience with videogames made for one flavor of Linux not working on my machine due to dependency hell.
Installing old Linux applications IS a problem. They’re available only if someone repackaged them for newer distros. If not they can’t run anymore because of dependencies mismatch.
Nah, skill issue. Get gud and resolve the dependencies manually. 🤓
It’s actually an ongoing problem with closed source Linux games. Devs don’t want to update, and don’t want to open source.
A lot of the time the Windows version will play better through Proton/Wine.
Flatpak time
NCSA Mosaic flatpak my beloved
Just supply the dependencies with a chroot. That’s how we did it before distro maintainers started including the 32bit libraries into the 64bit OS.
You got to build them shits from source.
First step install the old ass compiler version this can be built with.
This is a good reason for static linking. All the dependencies are built into the binary, meaning it is more portable and future proof.
We don’t need flatpak for this!
And harder to fix vulnerabilities in a linked library, and more bloat in both storage space and memory used.
Trade-offs!
I’ll take a program that isn’t getting updates anymore or simply doesn’t work in my modified environment using slightly more ram and storage over it not working at all.
I have firsthand experience with videogames made for one flavor of Linux not working on my machine due to dependency hell.