4 ms·
You are comparing Rails to Java, which is wrong because the first is a framework and the second a language. A fair comparison would be between Rails and Spring
by vladoh 15y ago
You are comparing Rails to Java, which is wrong because the first is a framework and the second a language. A fair comparison would be between Rails and Spring or Ruby and Java. And here things are different.
In Spring you also have clearly defined rules about the Model, View and Controller classes like in Rails. However you still get all the benefits of tooltip JavaDoc and auto-complete on . and Ctrl+Space (in Eclipse).
- ekidd 15y agoDespite the disagreement, I'll stand by my earlier remarks: Many popular Java frameworks involve a lot of boilerplate. I've never used Spring, so I can't comment on it. But in the last two years, I've worked on multiple GWT and Android applications, and both frameworks encourage people to write a lot of code for something as simple as MVC bindings. Seriously, GWT can easily require 10x as much code as Backbone.js + CoffeeScript. I'm impressed by newer Java frameworks like Play, which make Java look terse and flexible. And I agree that refactoring IDEs are amazing tools, and well worth some sacrifices to use. I merely disagree with skrebbel's remark that, The advantages of IDEs over text editors isn't look or feel. It's code quality. The are multiple, valid ways to achieve high code quality. IDEs are one of them. But there are real tradeoffs here, and other legitimate choices.