Thursday, May 24, 2012

Reason to use Ruby on Rails


Following are the criteria we should consider while selecting a Language
  •     One simple web page
  •     How media(css, js) is handled in the framework
  •     Connect to a database
  •     One table to store your data
  •     A form to save information into the table
  •     Deploy it live
RoR :
  • RoR is a DSL for webdev, the API distilled to its most pure form. Everything makes sense and can be expressed very easy. Highly readable.
  • RoR is community driven with no commercial entity nagging (springsource?).
  • the secret is not RoR (the framework), the secret is the Ruby language.
  • integrate with JVM via JRuby (mature technology)
  • Java to Ruby is easy (both imperative, object oriented, similar syntax)
  • simple web development, I had previous experience mostly with JSP/JSF, the Ruby approach seemed much simpler and "right" - MVC with simple reusable templates with a lot of helpers ready to be used + all the layers fill in nicely with each other.
  • I really leveraged/understood all kinds of testing - Ruby is full of great testing libraries and I think the Ruby community did most of today's testing innovations
  • You are always in control of the code, if You hit a bug in a library You can quickly deal with it, I know it might sound crazy to be able to "monkey-patch" everything, but it really gives You control over You whole application
  • Rails is more "database-oriented".
    In Rails, you essentially start by defining your tables (with field names and their specifics). Then ActiveRecord will map them to Ruby classes or models.
  • if you use JRuby or Jython, then your Ruby and Python threads are Java threads. So, they are not only as efficient as Java threads, they are exactly the same as Java threads.
  • Ruby seems like a neat platform where all the tools are at your fingertips. It was built to solve your problems fast. It's becoming the most popular on the startup scene

No comments:

Post a Comment