upvote
MacOS has the drawback today any software compiled more than x years no longer works.

That is an unforgivable sin in my eyes.

reply
IMHO - disagree but it depends on point of view so this is not ”you are wrong” but ”in my view it’s not like that”.

I think it’s the role of the software vendor to offer a package for a modern platform.

Not the role of OS vendor to support infinite legacy tail.

I don’t personally ever need generational program binary compatibility. What I generally want is data compatibility.

I don’t want to operate on my data with decades old packages.

My point of view is either you innovate or offer backward compatibility. I much prefer forward thinking innovation with clear data migration path rather than having binary compatibility.

If I want 100% reproducible computing I think viable options are open source or super stable vendors - and in the latter case one can license the latest build. Or using Windows which mostly _does_ support backward binaries and I agree it is not a useless feature.

reply
Yes Apple should have kept supporting 68K software and have emulators for 68K, PPC and 32 bit x86.
reply
false equivalence much?
reply
So exactly how far should Apple go back?
reply
Mac works great out of the box. Linux can do whatever you want if you put some work into it. Windows sits kind of in the middle, and it turns out for a lot of people that's a comfortable spot even with its trade-offs.
reply
Agree - there are variations to how much tweaking Windows needs.

Enterprise Windows config that comes eg in Thinkpads is more ready out of the box than the consumer OEM configss.

reply
They would still need to develop new drivers for new hardware, which could cause issues. But yes, the situation you describe would be much more stable than Win11.
reply