Ben, your comment rests on the idea that Carbon is a more accessible (or at least as accesible) programming environment as Cocoa. Nothing could be farther from the truth. The C language is more widely used, but Carbon is nowhere near Cocoa's refinement.
Any competent C programmer can learn Objective-C in a few days. That's as true now as it was ten years ago. It's about to become easier in Leopard. As for C++, a lot of people seem to be using Objective-C++.
Although you may think it's a "goofy" language, it's also a key reason for Apple's incredible productivity. Things like Core Data would be much, much harder without the benefits that Objective-C's runtime provides.
I like John Randolf's suggestion of looking at the documentation for NSUndoManager (which intercepts invocations at runtime) and describe how you would go about implementing that in Java. A lot of that applies to Core Data now, too.
For what it's worth, I think Rails catches a lot of the same flack for the same reasons.
by Scott Stevenson — Oct 26
Any competent C programmer can learn Objective-C in a few days. That's as true now as it was ten years ago. It's about to become easier in Leopard. As for C++, a lot of people seem to be using Objective-C++.
Although you may think it's a "goofy" language, it's also a key reason for Apple's incredible productivity. Things like Core Data would be much, much harder without the benefits that Objective-C's runtime provides.
I like John Randolf's suggestion of looking at the documentation for NSUndoManager (which intercepts invocations at runtime) and describe how you would go about implementing that in Java. A lot of that applies to Core Data now, too.
For what it's worth, I think Rails catches a lot of the same flack for the same reasons.