Rails vs Java. Kind of...
May 25, 2012

Lately I’ve been doing lots of Java development, J2EE. By no means is it a small
project, I’m using all sort of external libraries, and these, in turn, make the
project that much more complex. Coming from the Rails world, I have an appreciation for the good, the bad and the ugly. Hence, I’m at a good position to compare them both. However, this post isn’t about Rails vs Java but rather a quick summary of things to be aware of when using Java.

I’m sure many people will disagree with me here, and, as usual, there is not
right or wrong side.

I could write about their differences, the good, the bad, better/worse
about each language. However, that’s been already written many times.
Also, they both have their pros and cons and they vary depending on the application/environment.

That said, for me there’s one item/area that is worth writing about. That is, “simplicity and cleanliness” (yes, it’s a big item)

In Rails, and any of the new modernish languages, the code is cleaner/less verbose.
To me this is a big item because of the impact it can make in your code.
Having simple code makes your program easy to maintain, including adding/removing features becomes trivial,
which in turn makes it easy to write tests and lots of it! Which in turn makes your code
less prone to bugs!

It’s a spiral effect! Now imagine the reverse of this spiral effect: hard to add features →
pain to test → more bugs… Doesn’t sound good at all!

Just to be clear, I’m not saying Java is all of these bad things, in fact, Java is very
reliable, stable → SOLID. But in my experience, Java makes it simpler to fall in the spiral
of madness…

That’s all.

Aug 30,2014