3 ms·
> Technology can't simultaneously progress while still remaining backwards-compatible for years or decades. Yet I can run statically compiled Linux binaries fr
by heavyset_go 6y ago
> Technology can't simultaneously progress while still remaining backwards-compatible for years or decades.
Yet I can run statically compiled Linux binaries from 20 years ago just fine, and play Windows games that were released over 20 years ago, too.
- SuperscalarMeme 6y agoThat's because you're locked into the x86 paradigm. Look at the leaps and bounds Apple is making with performance/Watt by moving away from x86. This is the cost of legacy.
- posguy 6y agoArchitecture emulation like QEMU provides is commonly used, just a matter of how much investment is made into backwards compatibility by those who build your operating system/platform. Apple works hard to break backwards compatibility every few years, while other operating systems will happily run software from decades ago as they care and invest in not breaking userspace.
- yagya 6y agoApple really likes being on the bleeding edge of computers, and it often comes at the cost of older programs and features being killed off in that process.
- heavyset_go 6y agobinfmt_misc[1] would like to have a word with you. [1] https://en.wikipedia.org/wiki/Binfmt_misc https://en.wikipedia.org/wiki/Binfmt_misc
- spijdar 6y agoThe key is that they're statically linked. Even so, you will begin to run into some issues in that time frame. My last experience trying to deal with ancient Linux binaries on an ARMv5 device running linux 2.4 was pretty abysmal. There were some breaking changes in the mid 2000s, I believe regarding threading? Old executables wanted LinuxThreads while modern linux uses NPTL. Not sure though. Might have just been a userland/libc problem. Sometimes, even Linux breaks backwards compat to progress.
- deleted 6y ago[deleted]