41–50 of 277 posts
Does this mean that if you want to distribute a Java app bundle, you must package the JRE into it as a framework?
It doesn't prevent someone else from bringing Java 7 to OS X, nor does it mean that the existing support for Java 6 is going anywhere.
I wonder if putting the boot into the most straightforward cross-platform solution for desktop apps has anything to do with the proliferation of OSX Java apps with shoddy/un-maclike UX/UI or whether it's something to do with Oracle's recent moves.
Funny thing is, one of my favorite Mac apps was/is written in Java: Cyberduck FTP client.
Cyberduck is an open source app originally written using the Java/Cocoa bridge, then using some hybrid of Cocoa and Java. But the thing is, the end user has absolutely no idea that it's a Java application. The only reason I know it's written in Java is because I looked at their source code to see how they implemented Quick Look (before it was a public API), and boom, the damn thing's in Java! As a longtime hater of Java desktop apps, I was flabbergasted.
As far as I'm concerned, OS X was the only desktop platform where Java had any sort of chance for user acceptance, but it never caught on with developers. As such, Java has been effectively dead as an option for desktop development since OS X Leopard.
Earlier quoted context omitted.
is there such a proliferation? the only java app I use on the mac is cyberduck, and it is neither shoddy nor un-maclike
Had no idea Cyberduck is written in Java. If only all Java desktop applications are like this.
The main point seems to be: They don't use any of the Java GUI frameworks. They instead use some Cocoa bindings.
See here: http://trac.cyberduck.ch/browser/trunk/source/ch/cyberduck/u...
Sounds significant, but how important is Apple/MacOS to Java?
Not really as significant as one might think. This is just Apple saying, "we're discontinuing our own, internally developed and maintained JRE/JDK." I don't know off-hand how far this diverges from Sun/Oracle Java or IBM Java though (maybe someone else can step up with that information). I didn't see anything saying that they would never distribute any JRE on Mac OS X though. They may just find someone else's JRE to…
Earlier quoted context omitted.
"Their" up and coming MacRuby platform? Is that a joke?
Might I say, "the up and coming MacRuby platform Apple has designs for"? At least a couple of the committers are Apple employees. But I misattributed the project as being "theirs", which apparently isn't true.
For all its faults, Java does deliver something that resembles the "write once, run anywhere" dream.
Any idea for a high-performance, cross-platform, native UI development stack? Is C++/Objective-C still the best option?
Speculative, but could this be an early preventative measure to keep JRuby from challenging their up and coming MacRuby platform?
Wait, I thought Oracle (Java's current owner) is Apple's friend, because of the lawsuit against Google's Android. Head spinning.
Does this mean that if you want to distribute a Java app bundle, you must package the JRE into it as a framework?
No, it means that Apple is not bringing Java 7 to OS X. It doesn't prevent someone else from bringing Java 7 to OS X, nor does it mean that the existing support for Java 6 is going anywhere.
Does this mean that if you want to distribute a Java app bundle, you must package the JRE into it as a framework?
No, it means that Apple is not bringing Java 7 to OS X. It doesn't prevent someone else from bringing Java 7 to OS X, nor does it mean that the existing support for Java 6 is going anywhere.