Railed?

Everyone has been talking about Ruby On Rails lately. Everyone seems to be a bit defensive, unless they are a Ruby developer. The Java community seemed to be most defensive, since the RoR movement seems be motivated by Java's verbose, XML-hell of config files. (Note: despite being called a fanboy today, I consider myself completely objective when it comes to programming languages. Complaints may be sent to /dev/null)

We've got an internal application that I've implemented as both a Tapestry and 'Front Controller' style Perl. I suggested Jaxn implement the same application with Rails today, and he got it done in just a few hours.

My worries are:

• Complex 'pages' - Multi-page form submission scenarios come to mind.


• ORM - ActiveRecord seems to do a good job, but we have an ugly legacy schema ;)


• Libraries - Perl and Java have huge amounts of code to lean on. Can I encrypt and decrypt our credit card information?

I'll try and keep this page updated as we go along.

UPDATE:

• Complex pages seem to be ok.


• Remapping id's and what not seem to be ok.


• Libraries? What libraries? This worries me.

Comments

[Curt Hibbs]

For libraries, check RAA (Ruby Application Archive): http://raa.ruby-lang.org/

and RubyForge: http://rubyforge.org/