Comments on: Getting your feet wet with Ruby on Rails http://marc-abramowitz.com/archives/2005/07/29/getting-your-feet-wet-with-ruby-on-rails/ Thu, 15 Jul 2010 07:55:28 -0700 http://wordpress.org/?v=2.9.2 hourly 1 By: Marc http://marc-abramowitz.com/archives/2005/07/29/getting-your-feet-wet-with-ruby-on-rails/comment-page-1/#comment-208 Marc Fri, 29 Jul 2005 21:01:50 +0000 http://marc.abramowitz.info/?p=527#comment-208 Now that I had been through the process once before and worked out the kinks, a colleague and I decided to build another simple web app that we had been wanting for internal project tracking. Start to finish, it took 5 minutes this time. I wonder how well Ruby on Rails works for more complex applications... Now that I had been through the process once before and worked out the kinks, a colleague and I decided to build another simple web app that we had been wanting for internal project tracking. Start to finish, it took 5 minutes this time.

I wonder how well Ruby on Rails works for more complex applications…

]]> By: Marc http://marc-abramowitz.com/archives/2005/07/29/getting-your-feet-wet-with-ruby-on-rails/comment-page-1/#comment-207 Marc Fri, 29 Jul 2005 17:43:22 +0000 http://marc.abramowitz.info/?p=527#comment-207 The following article does an interesting comparision of PHP vs. Ruby on Rails and PHP wins for him. <a href="http://www.megginson.com/blogs/quoderat/archives/2005/06/11/rails-vs-php-mvc-or-view-centric/" rel="nofollow">http://www.megginson.com/blogs/quoderat/archives/2005/06/11/rails-vs-php-mvc-or-view-centric/</a> The author doesn't seem to have as much of a problem with Ruby or Ruby on Rails as he does with the general concept of MVC frameworks. His beef is that they work well for simple CRUD apps but then become untenable when you start working on more complicated apps with SQL queries with joins and such. An interesting point. I don't know if Rails or other MVC frameworks have ways of dealing with this. The comments are interesting. Another interesting thing is that people seem to mostly be concentrating on two-tier apps, where the server code accesses the database directly. These apps tend to be simpler which means that they can easily be written in straight PHP but they also can easily be achieved with something like Rails, which wraps the database with an object layer. The stuff that people do in J2EE tends to be three-tier architectures where there's a layer of business objects and business logic on top of the database. Perhaps Rails would be a bigger win in this type of situation? The following article does an interesting comparision of PHP vs. Ruby on Rails and PHP wins for him.

http://www.megginson.com/blogs/quoderat/archives/2005/06/11/rails-vs-php-mvc-or-view-centric/

The author doesn’t seem to have as much of a problem with Ruby or Ruby on Rails as he does with the general concept of MVC frameworks. His beef is that they work well for simple CRUD apps but then become untenable when you start working on more complicated apps with SQL queries with joins and such. An interesting point. I don’t know if Rails or other MVC frameworks have ways of dealing with this.

The comments are interesting. Another interesting thing is that people seem to mostly be concentrating on two-tier apps, where the server code accesses the database directly. These apps tend to be simpler which means that they can easily be written in straight PHP but they also can easily be achieved with something like Rails, which wraps the database with an object layer. The stuff that people do in J2EE tends to be three-tier architectures where there’s a layer of business objects and business logic on top of the database. Perhaps Rails would be a bigger win in this type of situation?

]]>