Quote:
Originally Posted by EUiPhoneUser 
I think you made a reasonable post, but I disagree. As in "totally disagree". I invested the last 10 years of my career to develop for Mac OS. The decision Apple made is good for me. You might not be aware, but Apple already tried the waters with Java when Objective-C was widely unknown outside of the small circle of NEXT developers and Java was the buzzword of the day. The idea that Java will help bring developers on board failed miserably back then. I was not a NEXT guy and learned Objective-C in 2-3 days. It was the frameworks that took much longer. Objective-C is not the best language on the planet by a big margin, but Apple had lots of reasons to stick with it, and they made the right decision.

I think you made a reasonable post, but I disagree. As in "totally disagree". I invested the last 10 years of my career to develop for Mac OS. The decision Apple made is good for me. You might not be aware, but Apple already tried the waters with Java when Objective-C was widely unknown outside of the small circle of NEXT developers and Java was the buzzword of the day. The idea that Java will help bring developers on board failed miserably back then. I was not a NEXT guy and learned Objective-C in 2-3 days. It was the frameworks that took much longer. Objective-C is not the best language on the planet by a big margin, but Apple had lots of reasons to stick with it, and they made the right decision.
I would have to pretty much agree with this, except for perhaps the size of the margin between Objective-C and the "best language on the planet"; I don't think it's that large. But, yes, an experienced Java programmer could learn Objective-C in a day. (Java is derived from Objective-C, after all.) And, as with learning to program on any platform, the language itself is pretty simple, the frameworks take 99% of the learning time.
I remember when Apple announced "Rhapsody", Mac programmers were freaking out about having to learn Objective-C. All those funny square brackets all over the place! How could they ever program like this! There were proposals to change Objective-C to use a C++ style dot notation (which, unfortunately, was added to Obj-C 2.0; amazing how many grown men couldn't deal with square brackets), proposals to make Java the programming language for Rhapsody, and so on. (They did move WebObjects to Java, which certainly didn't help there.) Fortunately, after a while, most everyone calmed down and realized that Objective-C wasn't really a big deal.







