In yet another demonstration that Madthumbs isn’t a developer just repeating AI nonsense, they incorrectly state that API compatibility is 100% maintained everywhere except linux.

Maintaining 100% API compatibility isn’t a good thing, and nobody (even Windows/MacOS), despite their claim maintains perfect compatibility.

The reason is:

  1. Some API’s have security issues and NEED to change
  2. Some may even try to do too much, or have issues with race conditions.
  3. Every OS has undocumented bugs in their API’s. Projects like Wine found many Win32 API bugs they need to replicate and implement. If a bug is found, the question becomes: do you modify the API to mention the bug, or do you fix the bug… Or, do you deprecate the API because its ambiguous? Microsoft allegedly uses Quirks hardcoded for certain apps to handle this…
  4. I’m not sure its a good thing to be “proud”, that an API isn’t evolving and improving.
  5. The easiest way to maintain compatibility, is to simply not do any improvements.
  6. API’s don’t break overnight. There is warning… If a app hasn’t received updates in 2-3 years, it shouldn’t be used in an enterprise settings AT ALL

In regards to “ABI compatibility”

  1. Apple charged CPU architecture 2x in the past 20 years. Some people who bought the Mac Pro literally only have 3 years of App support, and now their machine is junk. Rosetta 2 is going to be pulled completely soon, so NO Intel apps will work
  2. Apple also switched to 64bit apps only on IOS at one point, and pulled every app from the market that wasn’t compiled that way
  3. Its such a serious issue, that the NVIDIA DGX Spark uses linux
  4. So does the Steam Machine
  5. So does Meta Quest
  6. So do most servers
  7. So do many TV’s
  8. So do most Mobile phones
  9. So do most routers
  10. In the kernel, a lot has moved to userspace (even DevFS moved to udev). Which basically means it doesn’t matter

In case there was any doubt that Madthumbs has no idea wtf they’re talking about, I’d say its confirmed…