Microsoft abandon the entire API, and replace it with something new every couple of years (the grandparent comment has a good list). This has the benefit that once software does work it should continue working more or less indefinitely.
Apple have mutated the same API over many years, however Xcode's default settings drift, deprecations are frequent, and the new macOS is rarely backward compatible with a large application. This means that each summer when the new Xcode/macOS combination is released you have to spend some time getting up and running again.
I doubt that the ideal situation of a continually developed API with perfect backwards compatibility exists. In that case the getting your code building and running with the new Xcode/macOS each summer is likely less time consuming than rewriting against a new API every 5/10 years. If you are maintaining well established code, then the opposite is true.
I recently installed something that was probably first targeted Windows 98.
The APIs listed by GP are deprecated and the platforms are not shipped/enabled by default, but that's worlds apart from intentionally breaking them (with almost no communication).
Of course, I still prefer a good package manager and direct access to the source on GitHub/GitSomewhere, but MSDN is very well maintained.
Microsoft is a little weird. The safe bet for a desktop application is to do it in WinForms. I'm pretty convinced that Winforms will outlive any of the newer frameworks from Microsoft.
The XAML developers will jump to whatever the next thing is when it comes around, but the conservative WinForm developers won't go anywhere anytime soon, forcing Microsoft to continue supporting and developing Winforms.
Throwing together a quick WinForm application is still much faster than building something using XAML, in my opinion. Especially if you don't know what you're doing, and that still how many in-house business applications seem to be built.
MS has backwards compatibility for existing software, but it's a gamble to start a new project using MS tech, you don't know what they will cancel, rename or invent next year.
Apple doesn't have backwards compatibility for existing software and stuff breaks regularly from version to version. However, one can count on Objective-C to pretty much work (although Swift is still work in progress).
