Does an Open Java Really Matter?
snydeq writes "Fatal Exception's Neil McAllister questions the relevance of the recent opening of Java given the wealth of options open source developers enjoy today. Sure, as the first full-blooded Java implementation available under a 100 percent Free Software license, RedHat's IcedTea pushes aside open source objections to developing in Java. Yet, McAllister asks, if Java really were released today, brand-new, would it be a tool you'd choose? 'The problem, as I see it, is twofold,' he writes. 'First, as the Java platform has matured, it has become incredibly complex. Today it's possible to do anything with Java, but no one developer can do everything — there simply aren't enough hours in the day to learn it all. Second, and most important, even as Java has stretched outward to embrace more concepts and technologies — adding APIs and language features as it goes — newer, more lightweight tools have appeared that do most of what Java aims to do. And they often do it better.'" Since Java itself never mattered except to sell books, I still don't see why opening it matters.
Everyone knows Java is in heavy use in various industries
particularly Publishing and eCommerce :-)
"Slow JVMs. More syntax than C. Lame." -- CmdrTaco
As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
Java isn't just for selling books. Look at how many Java libraries are around.
No data, no cry
Pearl. All the other terms are correctly spelled?
No Multiple Inheritance. Slower than a 486. Lame.
C++ will always have a place in my heart & I'll use it when ever practical.
Don't you mean &&?
== Jez ==
Do you miss Firefox? Try Pale Moon.
I think Multiple Inheritance's primary use is for contriving strange interview questions. :)