Linked by snydeq on Fri 29th Jan 2010 15:59 UTC
Java Any doubts regarding Oracle's stewardship of Java were dispelled yesterday, as Ellison and company have made it clear that they are very interested in making Java an even stronger alternative to .Net, writes Fatal Exception's Neil McAllister. "We have the money to invest in Java, because Java is a very profitable business for us already," said Ellison, whose plan for integrating Sun technology is ambitious, serving an even more ambitious goal: to create a soup-to-nuts tech juggernaut akin to IBM in the 1960s. Java will remain a key component of this push, with a new Java runtime, greater modularity, better support for non-Java languages, improved performance, and multicore-optimized garbage collection in the works, McAllister writes. Also revealed are plans to unify the Java SE and Java ME programming models and APIs and to enable JVM to run natively on hypervisors, allowing developers to run multiple Java instances on a single virtualized server.
Permalink for comment 406712
To read all comments associated with this story, please click here.
Member since:

I doubt many Java devs care about TrayIcon support since Java is mainly strong in mobile devices and serverside applications. Desktop support (Swing) has been on the backburner for a while (maybe it will be reignited with the JavaFX RIA push).

As for non standard solutions; On the serverside Java offers JEE which has already made numerous choices for the developer. However there are also numerous open source projects/frameworks for all kinds of things which often offer a better fit for your project then JEE (Technologies like OSGi, Spring, Google Guice, and litterly thousands more). So yeah if you don't want choice, then with Java your going to have a hard time.

That's probably the biggest culture difference between Java and .NET developers. All the Java developers I talk to talk about different frameworks and the .NET developers only talk about the standard .NET frameworks. Java developers generally like their choices and .NET developers usually go with the solutions chosen for them by the .NET framework (I'm just pointing this out, I'm not saying one is better then the other).

Reply Parent Score: 2