Linked by Thom Holwerda on Tue 14th Nov 2006 19:02 UTC, submitted by Jane Walker
Java Monday, Sun did what many pundits, media personalities, developers and IT managers wanted done months ago - it opened up Java so that it could be freely distributed under the General Public License. In this interview with, Laurie Tolson, the vice president of Java developer products and programs, discussed this milestone for Java and what it meant for Sun, developers, IT managers.
Thread beginning with comment 182340
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Java ready for OSS?
by g2devi on Tue 14th Nov 2006 22:14 UTC in reply to "Java ready for OSS?"
Member since:

> Say what you want about Mono, but OSS developers have
> demonstrated it's usefulness in rapidly developing
> good applications.
Perhaps, but the same can be said about Java. Personally, I don't see much difference between Mono and Java on the desktop application's front. Both are pigs when it comes to resources and both have killer desktop applications (e.g. Java has Eclipse).

The only real weakness Java has is startup speed, since that it loads and JITs all libraries each time you load a Java program. This is actually not that difficult to fix (e.g. look at the Mac), but it needs a bit love to from the OS layer to implement the appropriate caches. Sun doesn't seem that interested in the Java desktop (the JSP area is where Java shines) and no-one else has been allowed to change "the official Java", so this part of Java has languished. But if distros are able to prepackage Java and versions of Firefox will be able to ship with Java, you can be sure that this issue will be taken care of.

Reply Parent Score: 3

RE[2]: Java ready for OSS?
by sbergman27 on Tue 14th Nov 2006 22:42 in reply to "RE: Java ready for OSS?"
sbergman27 Member since:

"""the JSP area is where Java shines"""


I think a GPL'd Java is great. But I would hardly say that web development is where it shines.

Reply Parent Score: 1

RE[3]: Java ready for OSS?
by g2devi on Tue 14th Nov 2006 23:38 in reply to "RE[2]: Java ready for OSS?"
g2devi Member since:

Actually it does. PHP and Rails are great for stand-alone apps or apps where you have small groups of people. JSP is probably overkill if that's all you need.

But once you get into Enterprise apps (i.e. apps that interact with dozens of other databases and apps) and large teams and legacy databases and interoperability with various vendors that you don't have the source code for, neither PHP nor Rails cut it and you have to pull out the big guns.

For instance, if you need to implement workflow management that obeys the XPDL standard (e.g. ), you'll have dozens of tools and libraries to chose from if you use Java (many of which are open source) and a couple are for .NET (all(?) of which come at a cost), but none for PHP or Ruby. You'll have to implement the standard yourself, and trust me on this -- it's not something you want to do (have a read on the specs).

Relating to the XML configuration, well, you don't need to do much of in Java -- if you chose the right framework and/or chose something Java attributes or XDoclet ( ). Most Java tools, like Eclipse also support fancy features like refactoring that just aren't available for lighter weight languages, so these tools really aid in making Java easier to use for larger projects.

Reply Parent Score: 4