By iterating on non-compatible releases, you're forced to run on the upgrade/rewrite hamster wheel to take advantage of that feature the last version didn't quite have but should've.
Joel Spolsky coined it "fire and motion" http://www.joelonsoftware.com/articles/fog0000000339.html
"Think of the history of data access strategies to come out of Microsoft. ODBC, RDO, DAO, ADO, OLEDB, now ADO.NET - All New! Are these technological imperatives? The result of an incompetent design group that needs to reinvent data access every goddamn year? (That's probably it, actually.) But the end result is just cover fire. The competition has no choice but to spend all their time porting and keeping up, time that they can't spend writing new features"
XCode and (Snow) Leopard? No such luck.
Now, you do mention the Linux alternatives, which seem to be the most stable... if you can get around any infighting of QT... Gnome/KDE... etc et al.
But it doesn't seem particularly "fair" to imply that this is something of a risk when you choose Microsoft.
They do give not-so-subtle hints to hand over to them the cha-ching, though, when they EOL old versions of XCode - but that's usually the most you're going to encounter. So works Apple in general.
And if you happened to bet on those technologies instead of Carbon, you're probably very happy with that. Well, unless you were writing Cocoa apps with Java, which was pushed as a peer to Objective-C in much the same way that Carbon was presented as a peer to Foundation and AppKit. Those technologies all got killed pretty viciously, even though Apple at various points actually seemed to be promoting them over Objective-C/Cocoa.
Apple axes stuff faster than Microsoft is even capable of moving. Looking directly back from their current technology stack, it looks like mostly smooth sailing, but that's because you're not looking at the wreckage to the left and right.
(Bonus points: Remember when Apple were all about Garbage-Collected Objective-C until they weren't and suddenly ARC was the new hotness?)
XCode and (Snow) Leopard? No such luck.
You can compile for Leopard and Snow Leopard by dragging the appropriate SDKs into /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/Option 1. Use a third-party abstraction library to make the same code work on every platform. Unity [1] is a popular commercial solution. FOSS solutions include jMonkeyEngine [2] (oriented toward PC games) and libgdx (with a focus on mobile) [3].
Option 2. Instead of writing for Windows, write for Wine. If your program runs in Wine, it should run in Windows (the reverse, alas, is not necessarily true). And you also get support for any platform Wine runs on, including not just Linux, but apparently Intel Mac [4].
[1] http://en.wikipedia.org/wiki/Unity_(game_engine)
[2] http://en.wikipedia.org/wiki/JMonkeyEngine
The only major piece to go away was Carbon, which was pretty much just for OS 9 backwards compatibility to begin with.
I use many of the same classes and techniques in iOS today that I did in the very beginning of learning OS X programming.
Apple for example takes a different route: they have shorter support spans, but rarely invalidate whole technology stacks. Cocoa is still alive and kicking after all those years.
Carbon programmers beg to differ.
(Full disclosure: I was always a Cocoa guy, so this isn't sour grapes. But if you were paying attention to the OS X development scene as a whole, it was really shocking how fast Carbon went from being more actively developed and having support for more things than Cocoa to being thrown straight into the dumpster.)
How is Cocoa still alive and kicking? How is that different from something like VB6?
Cocoa on the other hand is still the foundation of almost all OS X and iOS programs.
The situation is no different for other software vendors.
That is how commercial software works.
As a developer/analyst/admin that works primary in the MS application/data realms, I'm bummed out that MS can't communicate with developers and seems very disfunctional vision-wise. But as someone who also uses OSS software and OSS OSes, I'm not tied to their whims. Neither are a growing number of my clients...