Slashdot Mirror

← Back to Stories (view on slashdot.org)

Apple Freezes Java Support for Cocoa

Posted by timothy on from the like-a-moolatte dept.

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?"

11 of 154 comments (clear)

  1. Toolkits by yasth · · Score: 3, Interesting

    While it may not seem like such a big deal it complicates crossplatform toolkits, and the like. Of course the whole idea of having a "blessed" programming language seems rather old fashioned, and academic.

    --
    I'd do something interesting, but my server can't handle a slashdotting.
    1. Re:Toolkits by Frumious+Wombat · · Score: 1, Interesting

      Actually, this seems to be halfway to the Right Thing; you get rid of a non-portable extension to Java (good), but encourage people to use a minor (though clean) language for native-mode programming (iffy).

      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.

      --
      the more accurate the calculations became, the more the concepts tended to vanish into thin air. R. S. Mulliken
  2. What does this mean for WebObjects? by Millennium · · Score: 5, Interesting

    WebObjects 4.5 had support for both Objective-C and Java, if my memory's right. In WebObjects 5.0, support for Objective-C was dropped, because this was during the time when Apple Wanted You To Use Java.

    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?

  3. This only affects one app that I use... by Teancom · · Score: 4, Interesting

    Cyberduck. It's the only cocoa-java app that I use, or even know about (not saying there aren't more, just that I don't know about them). Following the cocoa mailing lists, questions about the java bindings are few and far between, which probably lead them to this point. Why dump so much time and effort into a language that your developers aren't using? Either redirect the manpower somewhere else entirely, or into a language like python, which gives your users a meaningful choice - between objc (lowlevel) and python (scripting). And applescript, I guess :-)

  4. Apple has been advising against integration for so by Hungus · · Score: 4, Interesting

    It has been considered best practice by Apple for some time to not use cocoa with java. Typically when someone has done this it has been for the GUI so that native widgets are accessible but with the Aqua widgets being accessible through Swing there is really no need for it now. If the argument is for cross platform writing of Java apps then pure java is always going to be more portable than Java + native elements.

    --
    Bad Panda! No Bamboo for you! In matters of importance ACs will not be responded to. Want to say something critical,OK
  5. What about SWT? by chroot_james · · Score: 2, Interesting

    I wonder how this effects swt or if swt can provide similar functionality to java-cocoa?

    --
    Reality is nothing but a collective hunch.
  6. Re:C++ is not a replacement by 1010011010 · · Score: 2, Interesting

    Objective-C coders don't use the language grudgingly.

    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.

    --
    Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
  7. Re:C++ is not a replacement by entrylevel · · Score: 3, Interesting

    I find it hard to believe you speak from experience. Did you write a program or did you just read some source code and figure some things out yourself? How long did you try at it? There's a lot to Objective-C, and being a superset of C is something I never saw as a detriment.

    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.

    --
    Karma: Incomprehensible (Mostly affected by posting at +5, reading at -1, and metamoderating everything unfair.)
  8. Re:History reconstructed (maybe) by metamatic · · Score: 3, Interesting
    When I interviewed at Apple in 97, the party line was that Java was going to replace Objective C as the standard language for accessing the NeXTSTEP APIs.

    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.

    --
    GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
  9. I you decided to use Java for your Cocoa apps... by 5plicer · · Score: 2, Interesting

    you should have listened to Aaron Hillegass IMO :p

    --
    The bits on the bus go on and off... on and off... on and off...
  10. Re:C++ is not a replacement by jiushao · · Score: 2, Interesting
    Python elegant? That's just ridicolous. Python is a huge and complex lanuage. It has ridicolously many language features, with a bunch new ones added with each release. All with only little planning and thought. It happens to end up being fairly powerful, and of course extremely featureful, but absolutely not elegant.

    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.