The Source for Java Technology Collaboration
User: Password:



Editor's Daily Blog

Poor Unfortunate Souls

Posted by invalidname on June 01, 2007 at 05:00 AM | Comments (5)

Mac Java developers keep waiting for JDK 6

It was hard not to notice all the Mac laptops at JavaOne, even in the general sessions, where the presentation stands often had three or four MacBooks lined up side by side for the demos. An uninformed observer might be inclined to think that the Mac was the best and most popular platform for Java development. They probably wouldn't suspect that the Mac is, in fact, nearly a year behind the Java mainstream, and not for the first time.

During JDK 6's development, Apple had been releasing Developer Preview releases of a JDK 6 implementation that were generally just a few betas behind Sun's official version. But when JDK 6 went final last fall, Mac users kept waiting, and are now still waiting, for a release-quality version for the Mac. The last drop, announced in September 2006, represents b88, a fairly late beta, but a beta nonetheless. While it's satisfactory for many, it still causes problems. For example, if you're working with JDK 6's programmatic access to javac, b88 still uses the class name JavaCompilerTool, while the final JDK uses JavaCompiler and has a few other API changes. The result is that you can't easily write a cross-platform app that uses this feature if you want to support the Mac, something I found out the hard way when I developed a Glossitope desklet that used this API (I still need to formally fork my code into Mac and non-Mac versions... what's on Josh & Rob's site now uses JavaCompilerTool and thus is still Mac-only).

Problems like these, compounded by the complete absence of any guidance from Apple about the situation, has some people asking if it's worth it. In fact, it has JavaLobby's Matthew Schmidt asking Is the Mac really a good dev platform? He's kicked off a lengthy discussion by asking "besides having a slick command line and nice interface, is the Mac really worth it for Java development? Your JVM version will always be behind, you're paying a premium for the Mac hardware and Apple has always treated Java like a bit of a second class citizen. So, why do you keep sticking with your Mac?"


Also in Java Today, the 123rd issue of the JavaTools Community Newsletter is out, with tool news from around the web, a list of new projects in the tools community, and a Tool Tip on converting your CVS-based java.net project to use Subversion.

In Java Mobility Podcast #6: Vodafone Introduces Betavine Developer Portal, Roger and Terrence interview Steve Wolak and Peter Thompson from Vodafone about the new Betavine site, a research and development space that encourages collaboration in mobile and internet communications. As a Betavine user, you can download and test applications, create your own projects and blogs, and interact with other users.


Apropos of the earlier topic of Macs and Java, the latest java.net Poll asks "Is the Mac a good Java development platform?" Cast your vote on the front page, then visit the results page for current tallies and discussion.


Today's Forums have one more Mac-related item, in which pepe asks about Java3D's status on osx: "In the company i work for we are actually checking various platforms for one of our upcoming product (netbeans and java3d based). We are investigating the use of a mac pro (with 4 geforce so that we have 8 displays.. yay!!). Has anyone used java3d on macs? What is your experience?"

aberrant has deployment problems on a different platform, in Launching a java application under windows: "Our product uses a batch file to launch our swing app. We are running into a problem though because Windows 2000 has a command line limit of 2047 and our classpath is starting to hit this limit. Is there some other way to pass the classpath to the JVM?"

Kirk Turner has some help for getting started in Project Wonderland in Re: Create a sample world: "I'm sure Paul et al will be able to give more information about this, but in the mean time, I've spent some time over the last couple of days modifying the world to use my own models. The first point of call is to have a look at the (wiki at the section about the Extending the world and Content Creation. The useLocalArt flag wasn't working for me, so I had to serve the content from my local apache (I added a few more instructions to the wiki for this). You then need to create your content and get it into a j3s format (compile java3d stream)."


In today's Weblogs, Carol McDonald has a tutorial on Pagination of Data Sets in a Sample Application using JSF, Catalog Facade Stateless Session, and Java Persistence APIs: "This Sample Store Catalog app demonstrates the usage of JSF, the new Java Persistence APIs, an EJB Stateless Session Bean to implement pagination in a Java EE 5 application."

Arun Gupta checks in with a href="http://weblogs.java.net/blog/arungupta/archive/2007/05/google_develope_1.html">Google Developer Day Report: "All in all, it was a great crash course for different Google offerings. It's a very long entry, so feel free to skip around, look at the pictures or read notes from sections of your choice."

Finally, Kirill Grouchnikov reports on major Substance development in Listening to the users part III - theme transitions: "A very small request has resulted in the most significant rewrite that I have made in the last two years. Read inside on what has happened."


Current and upcoming Java Events :

Registered users can submit event listings for the java.net Events Page using our events submission form. All submissions go through an editorial review before being posted to the site.


Archives and Subscriptions: This blog is delivered weekdays as the Java Today RSS feed. Also, once this page is no longer featured as the front page of java.net it will be archived along with other past issues in the java.net Archive.




Bookmark blog post: del.icio.us del.icio.us Digg Digg DZone DZone Furl Furl Reddit Reddit
Comments
Comments are listed in date ascending order (oldest first) | Post Comment

  • It's a great dev platform if you don't overgeneralize. Just because SOME Java developers are frustrated, doesn't mean a tacit conclusion about Macs as a dev platform. I'm totally enjoying my Mac for the Rails development I'm working on.

    Your narrow, dogmatic viewpoint is unproductive.

    Posted by: jolohaga on June 01, 2007 at 04:18 PM

  • the power balance between developers and apple has, as far as i can remember, been such that the developer is at the mercy of the vendor. i recall ten years ago reading messages just like yours on the webobjects mailing list, of users complaining about not knowing when a fix to bug x will surface. there were no apple engineers on the list. in fact, the list itself wasn't even hosted by apple. i happily write java code on linux. and i'm not deprived. all three major ide's: netbeans, eclipse, and idea (these days i use the latter most of the time) run on it. if i may say so, even ruby installs more easily on linux than it does on a mac. i recall reading one of pragdave's books where he details over several pages a hack for properly getting ruby to run on a mac. on my linux machine, it was a simple sudo apt-get install ruby or something similarly trivial. or perhaps it was already installed. i forget which..

    Posted by: eitan on June 01, 2007 at 04:39 PM

  • Developing in Java is fine. I do NetBeans quite successfully. But I am worried about using old, unpatched versions of Java. Even jdk 1.5 is at release .07 compared to the Sun version of .12. All those updates were security issues. Does this mean that OS X is not vulnerable to the problems, or that Apple is asleep at the switch?

    It the very least, Apple needs to tell its customers whether they are vulnerable, and if so, when a patch will be available.

    And yes, I need a newer 1.6, The java jdks now have different names when I switch from running NetBeans in 1.5 vs 1.6. This means I have to redo the libraries every time I switch.

    Posted by: jarome on June 01, 2007 at 10:32 PM

  • eitan writes: "reading one of pragdave's books where he details over several pages a hack for properly getting ruby to run on a mac"

    I'm sorry Eitan, but Pragdav hardly qualifies as an authority on Mac OS X, let alone installing anything on it. Unfortunately their popular books only confound the facts further (they're definitely coming from Mac as an afterthought mentality).

    You only have to download the Ruby source code and compile it (into /usr/local) or install the MacPorts package management system and install ruby just by typing:

    port install ruby

    This version gets installed on /opt/local.

    In any case, there's nothing on Linux system you can't do on a Mac system. You just need to know how.

    Posted by: jolohaga on June 02, 2007 at 12:13 AM

  • I share your concerns Chris. I was once buoyed by the early JDK 6 betas - but then there was just silence... I wonder what it will take for other vendors to supply JVMs now that they share the Intel platform...

    Posted by: jonmountjoy on June 02, 2007 at 07:59 PM





Powered by
Movable Type 3.01D
 Feed java.net RSS Feeds