MillieWe need to normalize declaring software as finished. Not everything needs continuous updates to function. In fact, a minority of software needs this. Most software works as it is written. The code does not run out of date. I want more projects that are actually just finished, without the need to be continuously mutated and complexified ad infinitum.
haematophage@millie unfortunately even if you do write a program that is feature complete, the sentiment towards backwards compatibility in the current landscape seems to be "lol who cares" so there's no guarantee it'll work in a year or two
datenwolfKernel APIs and ABIs are pretty stable on all relevant platforms. Just link statically, where applicable. Yes, graphics APIs are an issue due GPU drivers depending on dynamic linkage. However, if you can live without modern GPU, good old X11 depends on stable socket API only, and that's kernel.
@datenwolf @millie well yeah I mean I still use Athena- and Motif-based software when it's feasible and usually the biggest obstacle is GCC being a bitch. but everything else changes constantly ;p.
@haematophage @millie one of my off-time at-work projects is building a comprehensive suite of GCC, Clang, glibc and musl versions for a reasonably broad set of targets.
It's actually quite a challenge if you start from a recent version of GCC and glibc. Building an old version, like GCC-4.8 with GCC-12 is running into quite a few obstacles.
It's actually quite a challenge if you start from a recent version of GCC and glibc. Building an old version, like GCC-4.8 with GCC-12 is running into quite a few obstacles.