Apple Freezes Java Support for Cocoa 154
Nice2Cats writes "A little message on Apple's Developer Connection tells us that Cocoa for Java will get no new features after 10.4. The full text is:
'Features added to Cocoa in Mac OS X versions later than 10.4 will not be added to the Cocoa-Java programming interface. Therefore, you should develop Cocoa applications using Objective-C to take advantage of existing and upcoming Cocoa features.' Is this bad for Java, or bad for Apple, or bad for both, or doesn't anybody give a damn anyway?"
Toolkits (Score:3, Interesting)
What does this mean for WebObjects? (Score:5, Interesting)
Now, of course, it seems as though Apple Doesn't Want You To Use Java Anymore. Does this mean that WO6 will drop Java support, or at least bring back Objective-C?
This only affects one app that I use... (Score:5, Interesting)
Apple has been advising against integration for so (Score:4, Interesting)
What about SWT? (Score:2, Interesting)
Re:Toolkits (Score:1, Interesting)
I've always wondered why that piece of NeXT heritage stuck around, as I'd be willing to wager a doughnut (pick your favorite pusher) that there are more Ada-programmers around than Objective-C gurus. (translation: take a deep breath, wave goodbye, and move to C++ or whatever the modern alternative compiled language would be, or at least make sure the library interfaces are correct for both languages).
Actually, I'd be just as happy, since they have the entire GNU compiler collection, is to simply define a uniform calling convention for their libraries from all languages, and stop worrying abou the One True Language. DEC did it back in the 80s with the Common Language Interface, which allowed me to call the same function (with pretty much the same syntax) from Fortran, C, or Pascal. I presume today that would mean using SWIG to generate a common set of wrappers, and remembering that there are Fortran, Ada, and C++ programmers out there somewhere when generating them.
Maybe my memory is fuzzy, but it seemed simpler to call those functions than on Unix systems where I always have to worry about the library interface on a language by language basis (one underscore or two; case-sensitive or not, etc.) I would like that level of transparency back.
Re:C++ is not a replacement (Score:3, Interesting)
Since learning Objective-C, it's become my favorite C-type language. It's not something I have to use, it's something I like to use.
Re:C++ is not a replacement (Score:4, Interesting)
IMHO, it's far more elegant than C#, VB, or Java, used by millions (and loved by less). Certainly moreso than C or C++. It's not as elegant as Python, but few things are.
Most Objective-C programmers love the language a great deal and tend to be (at least on the Mac side) very vocal about it.
Re:History reconstructed (maybe) (Score:4, Interesting)
Yeah, well, it's worth remembering that back in 1997, Netscape's new browser was going to be written in Java, Corel were going to sell an office suite written in Java, and everyone was going to run 'thin client' systems based on Java. The great Java hype machine was just winding down.
I you decided to use Java for your Cocoa apps... (Score:2, Interesting)
Re:C++ is not a replacement (Score:2, Interesting)
C# and Java are both clearly more elegant designs, as is C really. C++ has a lot of syntax, and rather wacky semantics in parts, but it manages a lot of power with a few very important concepts (templates). Overall, in elegance I would probably rate Python second to last of the languages listed (VB is extremely unelegant). This does not mean that it is a bad language (though I personally don't care for it), it is powerful and featureful, but it pays for it by being a huge language.