Meh, that's more of an accessibility thing than stability. I agree it's dumb but you get a lot more with their developer program. Pro's outweigh the cons IMO.
Windows RT failed because Microsoft provided a shitty architecture transition strategy for their developer base. Not to mention the whole Windows 8 UX/UI disaster they put people through. Microsoft is just bad a making software. period.
To name a major few:
- Quartz ( Wayland wants to be this, but has failed for over a decade. Quartz was released in 2005(!) )
- AirPlay/AirDrop/AirPrint
- Continuity
- By-default app sandboxing
- Dynamic memory compression
- Thunderbolt GPU offloading
- Automatic GPU switching
- APFS (yes, the only stable filesystem comparable to ZFS)
As far as DE's are concerned. The desktop was already a solved problem when Apple inherited NeXT. Most (if not all) modern ideas came from NeXTSTEP.
OK, let's take a look:
-
Quartz: It's a graphics stack, not a protocol... It includes stuff like Core OpenGL and GPU offloading...
Wayland is a protocol in the same sense as HTTP. The two have very different purposes and designs.
- AirPlay/AirDrop/AirPrint : Something wrong with Samba/CUPS/VLC streaming over wifi? same thing. Avahi / mDNSResponder is in ports.
-
Continuity: Today I learned about it. And now that I know - another lock-in thing - it takes another Mac, AND you have to trust it. And no, I don't want to establish that trust every time I pay a visit to a new doctor and have to sign a truckload of paperwork before they agree to see me.
- By-default app sandboxing: There are Linux distros that actually do that. And that's not specific to a DE/WM.
- Dynamic memory compression: Why would that be specifically a desktop feature? There's plenty of ports that can be compiled with dynamic memory allocation option (yeah, not necessarily specifically memory compression). Granted, memory management is a sore issue with
www/firefox these days, but I don't think that memory management is totally nonexistent in the Open Source world. You do have to have a good handle on memory management techniques on different OS'es to be able to talk about why specifically 'Dynamic Memory Compression' is non-existent everywhere but Apple.
- Thunderbolt GPU offloading and Automatic GPU switching - This is a driver quality issue, not a desktop issue. Granted, Apple can handle modern GPU's better, and yes, that's most visible on the desktop. But, it's not a desktop issue, any DE/WM would be affected. Tying a DE/WM to a specific GPU driver is not good design.
- APFS
(yes, the only stable filesystem comparable to ZFS): Yeah, and in Apple, you can't just swap out a filesystem, install all your old stuff on top of the new filesystem and party.