Linked by Thom Holwerda on Wed 30th Apr 2008 13:04 UTC, submitted by someone
Back in 2007 when Apple released Mac OS X 10.5 Leopard, a much-heard criticism was the lack of support for Java 6. Leopard shipped with an older version of Java, 1.5, even though 1.6 had been released by Sun almost a year prior. Sun had already released Java 1.6 for Linux and Windows, but did not do so for Mac OS X, since Apple insists on developing their own version of Java, according to Sun. Now, 6 months later, Mac Java programmers can rejoice.
Thread beginning with comment 312141
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:
2006-05-14
I think it was Apple's choice not to have Java 1.6. Not Sun. Sun doesnt make a Java VM for Apple (or many other platforms). I think they support Linux/Windows and Solaris. From what i understand its up to Apple to develop and deploy Java on the Mac OS X platform.
Also, I am not sure what embedded system you are working with, but the J2ME works on lots of devices with as little as 5MB of RAM (some i suspect even less). If you are having to deal with JNI, it sounds like you are probably dealing with hardware that has no java library support. Thats not Java's Fault either (its like blaming language X for not having libraries for hardware Y, so you have to use an external interface to libraries written in language Z).
Java does not equal C. If you want C portability, use C. If you want Java's features, use Java. Or if you want the best of both worlds and your platform supports GNU GCC use Their GCJ compiler, and compile to native code and link to C/C++ libraries as needed. There are also more efficient VMs such as Kaffe.
BTW- i suggest if you are having problems with eclipse, use NetBeans. I have started using it for ruby development and its very nice.