A journey on Rails tag:rewrite.rickbradley.com,2005:Typo Typo 2006-08-13T18:19:50-05:00 rick urn:uuid:390ceba0-d8ba-4965-b64d-74c5e3bfed41 2005-11-16T10:32:00-06:00 2006-08-13T18:19:50-05:00

<p>In September (or so) we went through the process of trying to decide whether we wanted to keep plowing through the JBoss Java stack we were building with or to pursue an alternate technology. We did some test prototyping of part of our first component (of 6) in Ruby on Rails and then a test re-implementation of the full component in Ruby on Rails.</p> <p>The productivity increase (and code footprint decrease) was basically staggering. We undertook a full analysis of the consequences of shifting our development from our Java stack to a Ruby on Rails platform. Ultimately we decided to shift from Java to Ruby on Rails.</p> <p>The summary document of the issues (edited to protect the guilty :-) can be found on this site at <a href="http://rewrite.rickbradley.com/pages/moving_to_rails">Evaluation: moving from Java to Ruby on Rails for the CenterNet rewrite.</a></p>

<p>In September (or so) we went through the process of trying to decide whether we wanted to keep plowing through the JBoss Java stack we were building with or to pursue an alternate technology. We did some test prototyping of part of our first component (of 6) in Ruby on Rails and then a test re-implementation of the full component in Ruby on Rails.</p> <p>The productivity increase (and code footprint decrease) was basically staggering. We undertook a full analysis of the consequences of shifting our development from our Java stack to a Ruby on Rails platform. Ultimately we decided to shift from Java to Ruby on Rails.</p> <p>The summary document of the issues (edited to protect the guilty :-) can be found on this site at <a href="http://rewrite.rickbradley.com/pages/moving_to_rails">Evaluation: moving from Java to Ruby on Rails for the CenterNet rewrite.</a></p>