Live data from Hacker News

Apple deprecates Java

developer.apple.com

271–277 of 277 posts

Re: Apple deprecates Java

#271
post #158

Earlier quoted context omitted.

>SoyLatte Project Goals > - Support for Java 6 Development on Mac OS X 10.4 and 10.5 > - OpenJDK support for Java 7 on Mac OS X > - On-time release of Java 7 for Mac OS X

The project was always intended to help ensure continuity of Java on Mac OS X; integration with OpenJDK being the means to ensure ongoing support and encourage Sun/Oracle's adoption of official support for the platform. I've updated the project goals on the home page accordingly: - Support for Java 6 Development on Mac OS X 10.5 and later (including Mac OS X 10.7 Lion)

Awesome! :)

Re: Apple deprecates Java

#272
post #96

Earlier quoted context omitted.

Definitely. Unusable software is as bad as none at all. Unless someone is paying well, I'm not going to deal with the issues.

Well, if you have a choice, sure. But if you're working in a team where everyone uses Eclipse, it's really nice to have the ability to run Eclipse.

Eclipse should be fine since it's using their own SWT for the GUI. They're not using Swing.

Iv'e developed Swing for 10 years and I think it's basically botched. Sun had no clue about UI development, and Sing is the expression of that. Compared with the UI frameworks on OS X it's like night and day. But I digress - I think SWT is a much better approach in any case.

Re: Apple deprecates Java

#273
post #52

Earlier quoted context omitted.

GTK is trying to get there. Gimp was ported to MacOSX GTK--haven't checked in a while the state of the port. The Inkscape dev team at least has high hopes that GTK will become stable for MacOSX. http://gtk-osx.sourceforge.net/

I disagree with GTK, and I recommend Qt. I use several GTK apps on Windows and they don't look native. Furthermore, GTK has some deeply ingrained usability issues - such as the close button - that they bring to all platforms.

This is why Steve Jobs is against ALL cross platform development. Because it's going to be a lowest common denominator. At the same time, advancements on the platform are not going to be taken advantage of. Any new features in OSX would go unused - because it's not in the lowest common denominator. As a Java dev, I have to say he has a good point there. I just wish Objective C didn't suck so much.

Re: Apple deprecates Java

#275
CALM DOWN EVERYONE

Here's what Steve Jobs said in an email to a Java developer: "Sun (now Oracle) supplies Java for all other platforms. They have their own release schedules, which are almost always different than ours, so the Java we ship is always a version behind. This may not be the best way to do it."

To me, the sheer number of people using Java on the Mac in one way or another guarantee that it's not going anywhere. Apple isn't going to develop it anymore, but that may be a good thing. We'll see.

If Java apps can't be in the app store it would be a bummer. I don't see where it says that though - the app store rules say that you can't depend on deprecated tech. But it doesn't prevent you from shipping your Java based app complete with a Java VM - like you'd do on Windows.

Re: Apple deprecates Java

#277
post #106

That is very bad news for those of us who use Java on Mac OS X. And I don't mean UI programming, but developing server Java (or any JVM-hosted language, such as Clojure) applications.

Why? http://developer.apple.com/library/mac/#releasenotes/Java/Ja... The situation for Java will now be the same as that for developing in any programming language that Apple doesn't ship with OS X or that ships with a version lower than the one you are targeting. My suspicion is that Apple is likely to drop Java in 10.8 which gives ~3 years for the JVM community on OS X to get their act together making OpenJDK work…

One of the major reasons why we went with Clojure for a commercial project was the maturity of the JVM platform, particularly the HotSpot VM. We really care about multiprocessing, pauseless GC (ConcMarkSweep does a good job here), low memory situations, JIT optimizing our code and overall stability. HotSpot has been great so far.

I do not want to spend time on debugging VM or dealing with its issues. I've had that with Common Lisp and I don't want to go back there.

Post reply on HN