Access and Feeds

Technology: Which Way For Java?

By Dick Weisinger

Java Developers had mixed feelings about the news this past week that IBM plans to buy Sun Microsystems. Sun has long been criticized by developers in mismanging Java as a technology. They’ve been slow to open-source Java and heavy-handed in wielding control of the JCP [Java Community Process] for creating Java extensions. On the flip side, IBM has shown more willingness to partner with the Java community, making important contributions to Java development, like the Eclipse IDE and open source libraries.

But both Sun and IBM are guilty of moving the Java language from one that is quite simple to one that is “enterprise-style”, bloated and complex. Some worry that a combined IBM-Sun will only ratchet up the Java’s corporate heavy-style attitude.
Rod Johnson’s SpringSource company built the Java framework called Spring that creates solutions in a much more light-weight way. He commented on the proposed IBM-Sun merger that: “the parents of the old enterprise Java complexity are finally getting married, but it no longer matters. IBM and Sun are no longer critical to innovation in the enterprise Java arena… Java must get lighter. Java must offer a more joined up experience. Java must advance into the new world of the cloud and big developer productivity. If Java does not make a big move to the cloud then Java will become a legacy platform.”

But like any merger, there will also be casualties. It’s likely that some of Sun’s software products will be hig hardest — products like GlassFish and NetBeans will most likely be phased out.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Google Buzz (aka. Google Reader)

Leave a Reply

Your email address will not be published. Required fields are marked *

*