0 Rails versus Java web frameworks

        There are many other web application frameworks other than Rails. Apache Cocoon, Apache Struts, AppFuse, Google Web Toolkit, Grails, Hamlets, Spring Framework, Tapestry are frameworks just to name a few. This blog post compares Rails framework with these other Java frameworks.

Vastly reduced code footprint – Field results place productivity increases over modern Java methodologies (e.g., J2EE, Struts, etc.) in the 10-fold range.

Minimal configuration – Rails applications require a few lines of specification to identify each database connection you will use, as well as a line of configuration for each different type of routing you will use (typically 3-4 lines for an entire application). Both of these are necessary in any environment. By contrast, rather than the 20 or so lines required in a Railes application, typical medium-scale Java applications require thousands of lines of XML configuration, many of which are stronglycoupled across application layers.

IDE automation not required – Much of the productivity improvement in Java comes from the widespread use of tools to automate code writing and change. In comparison, Rails productivity improvement is based on the ease of programming it offers.