4 ms·
There's not a lot of content in this article frankly. I also suspect the author has either never been exposed to an 'enterprise' J2EE or Spring app, or has simp
by squidsoup 14y ago
There's not a lot of content in this article frankly. I also suspect the author has either never been exposed to an 'enterprise' J2EE or Spring app, or has simply forgotten what a labyrinthine nightmare those could become. Rails is more complex today, but it is still significantly easier than traditional Java frameworks.
- tmo9d 14y agoI suspect that your suspicions are wrong because I wrote the article and I spend much of my day writing both Java and Ruby. I just find it easier these days to work with Spring 3. Why? Because the Spring and the Oracle folks reacted to Rails pretty quickly and came up with a lot of solutions that might surprise you. It takes just about the same LoC now to do in Spring what I'm doing in Java. The difference is that the performance in Java is much higher.