There’s probably a fortunate 500 company running some load bearing server from 20 years ago, that ends up back in production, everytime they fail to migrate the critical service away from it.
There must have been demand to keep x86 32bit alive this long.
Well if you still like your hardware, and want continued, updated, software support, one of the BSD’s still likely to get you there for a bit longer. NetBSD likely being the one that drops it last.
But at some point, as long as you able to do your work and copy data back and forth, does it matter. Even just running winXP or 7 will get you along for sometime.
FreeDOS will always support x86, lol.
At least you not running something with an old big edian PowerPC machine. Support for those suck!
Does the machine a a socketed CPU, it appeared it runs the Core2 CPUs, if you get a core2duo, those support 64bit. I have a ThinkPad x60 with a 32bit Core2 CPU. It’s odd that there was 32bit only version of that class of CPU. I haven’t bothered to try upgrade it though.
I would recommend looking into the BSD’s, they have stronger support for older and unusual architectures. Something like nomadBSD, uses xfce on freeBSD
Bold of you to assume I don’t like using plastic donuts of data.
Fun because you like rewriting existing code?
Fun because you already have test suites you don’t have to rewrite?
Fun because you feel morally superior by writing fresh code, even though the old code is running critical applications in production?
Fun because you think your smarter than the engineers that lay the ground work before you?
Fun because you like hunting bugs you created thinking you know better, while calling your rewrite superior.
17 year old project that still cannot match it’s predecessors…
Considering they have an active GitHub repo, likely recently. Even more so with the BSD’s incorporating it as a default.
The BSD’s are embracing xlibre, so it is a project that’s being taken seriously and has real technical merits.
It probably runs payroll and no one is willing to miss a paycheck due to a botched updated