>>108896415being the uneducated nocoder pleb that I am, I spent some time looking into this and I have no fucking idea what you're rambling about
>https://aput.net/~jheiss/aout_redhat.shtmlthis is a 24 year old page, and I'm pretty sure the author conflated a.out with COFF when they're different formats
>Can even run COFF binaries todayas far as I can tell, COFF never gained any traction on Linux (aside from whatever the fuck ECOFF on MIPS is)
>You can't run a DOS binary on any windows machine today. The last time that was possible was on win95NTVDM and WoW16 persisted in 32-bit Windows for decades and they're still usable in x86 Win10
>Still true today with ELF-based adaptersThis is technically true, but translation layers ≠ native support, and even then, I don't see how using some unmaintained a.out -> ELF wrapper is any different from using WineVDM to run Win16 apps. I'm also conveniently ignoring that a.out was so short-lived on Linux that the only example of it I've seen is the Atari Jaguar linker and that it isn't an "ELF from the early 90s"
>Diablo 2 needed to be updated in 2016 to even run on windows 10I know jackshit about Blizzard games, but it seems like Diablo 2 ran on Windows 10 with basic workarounds even before that update
https://www.youtube.com/watch?v=dgyw4rD87jo>So the source is real life, while your source is your asso-okay :(
>>108896583>Windows XP software definitely does not run without issues on Windows 11Backwards compatibility on Windows has definitely gotten worse (especially since 24H2), and people tend to overexaggerate its quality, but I still think there's a difference between some 20+ year old games and programs needing unofficial tweaks, as opposed to shit on Linux outright breaking unless you recompile it for modern glibc/GTK/etc.
while I was writing this, I remembered that I've seen people hack old Loki ports like SimCity 3000 into running on modern Linux, but doing that shouldn't be necessary in the first place
