11–20 of 277 posts
Note that they've only deprecated their own Java runtime .
Note that they've only deprecated their own Java runtime .
I have not done Java development on OS X, but doesn't this mean that OS X 10.7 would not ship with a Java runtime? Wouldn't this have a negative effect on the ease of packaging and distributing Java programs on the platform?
Not, but it does mean 10.7 may ship without a Java runtime:
> This means that the Apple-produced runtime will not be maintained at the same level, and may be removed from future versions of Mac OS X. The Java runtime shipping in Mac OS X 10.6 Snow Leopard, and Mac OS X 10.5 Leopard, will continue to be supported and maintained through the standard support cycles of those products.
Note that they've only deprecated their own Java runtime .
Sidenote: I can only imagine the guy who wrote "Java Deprecation" in h2 font-size 187%, jiggling inside at the moment he did.
EDIT: I understand it's only a "possibility of removal", yet if I started working on a JVM-based app/product right now, I would be concerned.
Note that they've only deprecated their own Java runtime .
I have not done Java development on OS X, but doesn't this mean that OS X 10.7 would not ship with a Java runtime? Wouldn't this have a negative effect on the ease of packaging and distributing Java programs on the platform?
Note that they've only deprecated their own Java runtime .
On the other hand, is there really any other? For years, Apple has been pretty much the sole provider, and had their very own JVM with specific look & feel customization to the UI packages. The only real alternative is Soylatte[0], which is fairly purpose-specific. [0] http://landonf.bikemonkey.org/static/soylatte/
Apple has been pretty much the sole provider, and had their very own JVM with specific look & feel customization to the UI packages.
So was it their own separately developed JVM or just a bunch of additions to make the UI not suck on OS X?
Note that they've only deprecated their own Java runtime .
I have not done Java development on OS X, but doesn't this mean that OS X 10.7 would not ship with a Java runtime? Wouldn't this have a negative effect on the ease of packaging and distributing Java programs on the platform?
The issue has always been that Apple has maintained their own JRE code base, while Sun had maintained all of the other JRE's for the other OS's.
I've been doing Java dev on OS X since OS X came to be, and it's always had problems. Apple was constantly late in implementing features that were in all of the other JRE's, and it was a real pain to deal with across the different OS's.
Does this mean that if you want to distribute a Java app bundle, you must package the JRE into it as a framework?
Speculative, but could this be an early preventative measure to keep JRuby from challenging their up and coming MacRuby platform?
Earlier quoted context omitted.
On the other hand, is there really any other? For years, Apple has been pretty much the sole provider, and had their very own JVM with specific look & feel customization to the UI packages. The only real alternative is Soylatte[0], which is fairly purpose-specific. [0] http://landonf.bikemonkey.org/static/soylatte/
I don't own a Mac. Apple has been pretty much the sole provider, and had their very own JVM with specific look & feel customization to the UI packages. So was it their own separately developed JVM or just a bunch of additions to make the UI not suck on OS X?
Wait, I thought Oracle (Java's current owner) is Apple's friend, because of the lawsuit against Google's Android. Head spinning.