In the Linux world, instead of a proud "excuse" on a blog, a problem like this would kindle a discussion for a few days on the newslists, and a solution would be proposed and implemented in the following two months, to be accepted in the mainline a week afterwards. In macOS, this problem might stick around for a while, but Apple is forward-thinking enough to find better solutions eventually for problems that aren't necessarily vital but still should be corrected. For Windows, I doubt this will ever be fixed unless they do away with drivers as we know them entirely.
That's true, but then of course you would end up breaking compatibility with lots of things.
Linux has their drivers in the kernel tree for the most part, with no promise of backwards compatibility whatsoever. macOS is fine overall, but I've never had a major update not trash major parts of the OS, whether that's the build environment, some subset of GUI apps, or general hardware support.
Windows has a driver model. While not a promise, third parties can typically expect drivers to keep on working. I've never experienced an OS other than Windows with such broad hardware compatibility and such broad binary compatibility. Except in rare instances, just about every piece of non-driver software from the Windows 95 era works unmodified on modern 64-bit Windows. AMD64 did not exist when Windows 95 was released. Drivers also typically work unmodified, the major exception being a pretty significant change around the time of Windows Vista.
The Linux "solution" would be to yell at the driver maker to contort their driver to fit the Linux model and put it in tree. A vendor that refused would need to have their driver installer manually blacklist the kernel driver, and get support calls whenever the kernel's updated because the abi breaks again.
This is true for proprietary drivers, but the many open source drivers and replacement drivers would be fixed by someone in the next weekend after a kernel update, for ABI changes this minor. It might bother the single developer, but after the patch is distributed, it's completely transparent to end users, unlike Windows where you usually need to force every user to manually download the new update.
