The most important thing Apple should do is create sample *Cocoa*
applications - not command line ones. This way, they could explain how
audio is supposed to run as a background thread that can be
interrupted by a UI control.
I suspect that they simply didn't want to create special projects for
Cocoa and Carbon, but since Carbon is officially a dead end, why not
make all example Cocoa-only?
Well, I for one am glad that Apple continues to provide examples in C++ (read: non-ObjC). Many (if not most) of us have to make our apps work on Mac OSX and that other platform -- you know, the one with the 90%+ market-share called Windows. Writing all of the code twice (once in ObjC and once in C#) is just _not_ an option most of the time, so i'm quite thankful, as a full-time cross-platform developer, that I can code 90% or more of my app in C++, and only the platform-specific bits in ObjC or C#. ObjC is a cool language, I completely agree (the more I do it, the more I enjoy it) -- but so is C#, and when each camp demands that we drink their Kool-Aid, those of us who have to code for _both_ are really turned off. C++ is not the greatest language ever, but it's a very good object-oriented language to do professional cross-platform work in.
