There was the Object Pascal Toolbox, replaced by C Toolbox (MacApp), replaced by MPW, replaced by PowerPlant, replaced by Carbon, replaced by Cocoa.
I can list many other examples, even Cocoa has lots of deprecated APIs since OS X 10.0.
While Apple floundered during the 90s with their OS strategy, their API strategy in OS X has been absolutely rock solid.
It's now 2016, Carbon has come and gone as it was intended to and Cocoa is still around and is still the API you use for working with the Mac. If you're trying to do something on the Mac, there's going to be a single officially supported way to do it and that's it (if it's supported at all).
Meanwhile, there are three totally different frameworks on Windows that you can use to do the same thing, all of which are officially supported and none of which are deprecated.
There are quite a few 32bit apps making use of it and they will never be ported to Cocoa.
> Meanwhile, there are three totally different frameworks on Windows that you can use to do the same thing, all of which are officially supported and none of which are deprecated.
Win32 and MFC are deprecated for new applications, the way forward is UWP with XAML.
Project Centipede is just for porting existing code into UWP world.
Windows Forms was officially deprecated at BUILD 2014.
That's not a bad thing. It means if I wrote an app 5, or 10, or 15 years ago, I can keep working on it and updating it without having to throw most of the code away and start again.