Does J2EE belong to the past or the future ?
Most experts seem to be heading towards relegating java to the past when it comes to web development. And in someways I do agree. Anybody who has done any development in J2EE vs Rails or PHP will tell you how much faster it is to get an app up and running in Rails or PHP compared to Java.
The more I see rails the more I like the simplicity that Rails has brought to web development on Ruby. Just think of developing web apps in J2EE apps.
In rails
Install Ruby, the Rails gem and you are pretty much up and running
In J2EE to get the equivalent functionality
- Pick a Container – Tomcat, GlassFish, WebSphere …. (In some cases you might have to install jstl seperately.)
- Download and setup Hibernate (Core ,EntityManager , Annotations )
- Download and setup Struts
- Commons jars
- Log4j
- And then spend a long time unraveling the jar file dependencies of all the above packages to make them work together.
But does it really have to be that way – is it the fault of Java or the overly complicated frameworks that have sprung up around it – or even the complexity of J2EE itself. Maybe fixing the frameworks can get re-establish Java as the language of choice for web development.
Filed under: Uncategorized | Leave a Comment
Unknown Feed- An error has occurred; the feed is probably down. Try again later.
No Responses Yet to “Does J2EE belong to the past or the future ?”