Skip to main content

Is Java Too Bloated

Even though I have been programming in Java for several years, I am a bit displeased with the way Java and the J2EE platform has evolved. It seems like carrying a huge burden while programming, a burden that does not add much value.
Think of the amount of things we have to know while developing J2EE applications. For building a small application developers must be familiar with:

The Java language
The core Java API
JDBC
Servlets
JSP + Tags, EL
Struts (or another MVC framework)
Hibernate (or another OR tool or EJB's)

Learning these technologies takes a long time, but after learning one also has to keep himself updated on these technologies, and we know the rapid rate at which stuff changes in the Java world.

When we make a simple web based application, beyond the source code we deal at least with 3 configuration files; web.xml, struts-config.xml, and hbm.xml, not to mention the developer needs to know about packaging a J2EE application using jar, war, ear, ... files.

All this seems like way too much work to make small to mid sized applications. Sure the technologies have value, but the effort is disproportionate to the value recieved in terms of 'programmer productivity'.

Maybe we do need all these formalisms and specifications for large distributed applications, or maybe not. I am not sure, but I am sure that we do not need them for small to mid sized applications.

If anyone has had experience developing large distributed applications in a language other than Java, like PHP, Python, or Ruby, then please share your experience with us.

Comments

Gaurav Vaish said…
And what I say is... "Unless Java graduates, .Net will kill it" :)
Anonymous said…
Yes Java is trying to be everything for everyone. They have to stop the feature bloat, and focus on a distinct area.
Anonymous said…
(guess the comment is a bit late :-) ) however i would like to draw a parallel between bloating of Java( from core java to what it is today) and Republic of India( from n number of princely states to what it is today). At least in case of Java one can say that a lot of planned effort has gone into its making thereby making it much more 'predictable'. Compare it to the State of india which though progressive, one would be a bit hesitant to attach the word 'predictable' to it.

And with the advent of IDEs, the pain of 'bloating' is eased a bit, as many Mundane tasks are taken care by the IDEs themselves.This is not to say that new things are not to be learned.

Popular posts from this blog

My HSQLDB schema inspection story

This is a simple story of my need to inspect the schema of an HSQLDB database for a participar FOREIGN KEY, and the interesting things I had to do to actually inspect it. I am using an HSQLDB 1.8 database in one of my web applications. The application has been developed using the Play framework , which by default uses JPA and Hibernate . A few days back, I wanted to inspect the schema which Hibernate had created for one of my model objects. I started the HSQLDB database on my local machine, and then started the database manager with the following command java -cp ./hsqldb-1.8.0.7.jar org.hsqldb.util.DatabaseManagerSwing When I tried the view the schema of my table, it showed me the columns and column types on that table, but it did not show me columns were FOREIGN KEYs. Image 1: Table schema as shown by HSQLDB's database manager I decided to search on StackOverflow and find out how I could view the full schema of the table in question. I got a few hints, and they all pointed to ...

Commenting your code

Comments are an integral part of any program, even though they do not contribute to the logic. Appropriate comments add to the maintainability of a software. I have heard developers complain about not remembering the logic of some code they wrote a few months back. Can you imagine how difficult it can be to understand programs written by others, when we sometimes find it hard to understand our own code. It is a nightmare to maintain programs that are not appropriately commented. Java classes should contain comments at various levels. There are two types of comments; implementation comments and documentation comments. Implementation comments usually explain design desicisions, or a particularly intricate peice of code. If you find the need to make a lot of implementation comments, then it may signal overly complex code. Documentation comments usually describe the API of a program, they are meant for developers who are going to use your classes. All classes, methods and variables ...

Inheritance vs. composition depending on how much is same and how much differs

I am reading the excellent Django book right now. In the 4th chapter on Django templates , there is an example of includes and inheritance in Django templates. Without going into details about Django templates, the include is very similar to composition where we can include the text of another template for evaluation. Inheritance in Django templates works in a way similar to object inheritance. Django templates can specify certain blocks which can be redefined in subtemplates. The subtemplates use the rest of the parent template as is. Now we have all learned that inheritance is used when we have a is-a relationship between classes, and composition is used when we have a contains-a relationship. This is absolutely right, but while reading about Django templates, I just realized another pattern in these relationships. This is really simple and perhaps many of you may have already have had this insight... We use inheritance when we want to allow reuse of the bulk of one object in other ...