Java is having a bad year with Apple

http://www.computerworld.com/s/article/9232566/Apple_tries_to_kill_its_own_Java_on_most_Macs



This might affect the ease of use of JME browser apps in future :frowning:

uh…it doesn’t mean that java disapear from OSX…it’s just that now it’s gonna be provided by Oracle.

Actually i’d be more confident in a Java provided by Oracle than a java provided by Apple…IMO that’s pretty good new.

Yes actually thats kinda good, you canf inally relie on the mac osx stuff to do the same as it is suposed to be.

(Also it will no longer drag down the evolution, as apple is lagging a few releases behind usually)



The only current problem with this is, that currently lwjgl on mac with oracle jvm does not work.

Yes I also think this way its better, there were a lot of issues with Apples Java over the years. Ofc it was convenient that it was preinstalled but w/e. A problem at the moment is that lwjgl is not working on oracles java yet on mac :frowning:

1 Like

Just out of curiosity, why doesn’t lwjl run on Oracle’s mac jvm? Isn’t java bytecode supposed to be platform independent so it runs on whatever OS you give it?

@javagame said:
Just out of curiosity, why doesn't lwjl run on Oracle's mac jvm? Isn't java bytecode supposed to be platform independent so it runs on whatever OS you give it?


You do understand that lwjgl is basically a native library, right? It's a Java wrapper for OpenGL using JNI. All kinds of issues can crop up in that case.
1 Like

If only everything worked how it was supposed to…

1 Like

Yeah, there is no “java opengl” library and if there was it would also call native methods in the end, just like java itself :slight_smile: So instead theres things like lwjgl or jogl that allow using the OpenGL C api from java. Thats what we always mean by saying “theres no difference” to using a “native” engine, you call the same OpenGL API.