Posted by invalidname
on December 7, 2005 at 2:26 AM PST
Chapter 7 looks at Ruby on Rails in detail, considering it as an alternative to the usual combination of enterprise frameworks (e.g., Spring + Hibernate, or EJB) used in Java web applications. To justify this coverage, Tate recalls his first experiences with RoR:
"As I've said, I worked with a company that builds safety software for a manufacturing plant. We effectively build a web user interface to manage a complex domain model. We decided to build this application with a lightweight Java stack of Spring, Hibernate, and Web Work. We moved pretty quickly, and were pleased with our progress. We were proud of our accomplishments, because we'd rewritten a one-year Microsoft application in four months with Java. Naturally, as we accumulated a bigger code base, coding began to take longer.
Over time, Dave's arguments nagged at my subconscious. Dave and my business partner had the same conversations. As luck would have it, over the same week, we tried building a part of the application in Rails. I banged out the model and scaffolding in a couple of days. With his stronger HTML experience, Justin got further than I did. He actually implemented the whole application in Rails in four nights. The Rails version shocked us in another way--it was actually faster!"