Ruby on Rails Sucks? I Don’t Think So

I have been playing around with Ruby on Rails for a while. You know how to program and know the commands for it, you’ll think it’s cool. Ruby on Rails is a MVC framework for the language Ruby. MVC stands for Model-View-Controller. The model is the database logic, the controller is the application logic, and the view is the presentation logic. Using this style, it keeps things organized.

People will think Ruby on Rails suck because they don’t know how to catch on to it. I admit, I was originally one of them, until I read Agile Web Development with Rails, Third Edition (Amazon). This book showed me how powerful this framework was and how much it was capable of doing. Doing validations is a breeze, embedding variables and Ruby code is a breeze in the views, routes are easy to configure (no .htaccess), database migrations to keep things in order, ActiveRecord to ease querying, updating, and inserting (no more SQL queries), and there’s so many other cool things with it. There is even loads of plugins on the Internet and on Github that do kickass things.

Does Ruby on Rails use a lot of RAM? From what I have notice from playing around with it I haven’t notice it take so much RAM. Besides, if I needed more RAM later and I was generating the money from the site, I’d just upgrade the server, piece of cake.

I plan on developing new sites using Ruby on Rails. PHP is just getting old (the new namespace delimiter is \, and that’s an escape character!)

Comments

  1. Totally agree with you on that, i started learning RoR about a month ago using the same book, i was a PHP guy but once you go the Ruby on Rails way you don’t want to try anything else, it just lets you focus on what you want your website to do and saves you a lot of time.

  2. I’m agree too. I’m on my second project with RoR and it’s just amazing. I got a Java project (I’m new to Java too) and now I understand why RoR moto is ‘Development that doesn’t hurt’… I used to be a php guy too, and I can’t stand to that level of non-standards anymore.
    RoR is everything everybody always wanted to work with (and a lot of thanks to Ruby here)

  3. I’m RoR beginner (only 3 months) coming from Java (Spring, Hibernate), and C# (ASP.Net MVC, NHibernate)

    I think, Active Record is a Hell for good models: It’s impossible to derive a good data model from UML using active record (Thinks like inheritance, composites,…). Ruby on rails Models are, basically, a direct talbe ‘mapping’, not really an ORM…

    I specially hate thinks like ‘belongs_to’ and ‘has_many’, ‘has_one’… association, usually, are not a composition but Active Record gives us this vision.

    In the other hand, rails gives “freedom” to the programmers for ‘business rules’ breaking: you can’t isolate a robust model because Models exposes database ‘as this’ and complex repository operations must be implemented by the controller calling 2 or more model save, destroy, and so on.

    Finally, modern languages gives you the possibility for projects modularization (N projects in th same solution): each one with it’s own tests, etc… with Rails, it’s impossible to implement a model project and N different applications over this model… ALL IS STRUCTURED IN ONLY 1 PROJECT WITH 1 APPLICATION (that includes views, controllers and models). A framework that is thought with this structural restriction is really a bad solution (try to implement a backoffice and a web sharing the same model… no one in R&R gives a real, simple, DRY solution)

Comments are closed.