This post originated from an RSS feed registered with Ruby Buzz by Guy Naor. Original Post: How Rails Change The Backend Coding Effort Feed Title: Famundo - The Dev Blog Feed URL: http://devblog.famundo.com/xml/rss/feed.xml Feed Description: A blog describing the development and related technologies involved in creating famundo.com - a family management sytem written using Ruby On Rails and postgres Latest Ruby Buzz Posts Latest Ruby Buzz Posts by Guy Naor Latest Posts From Famundo - The Dev Blog

One thing I lately noticed, is that Ruby on Rails completely changes the work distribuition between the backend and the rest of the system.

In my past projects (C++ on Windows - see my first post), the backend took a significant amount of work just for writing and reading the objects in the databse. When you also take into account all the code needed to set up the connections, handle the associations and other related stuff and DEBUGGING you end up spending 30-40% of the time on the backend.

With rails it goes down to about 5% of the time, leaving much more time for the business logic of the application and the UI.

I just wish we had something as beuatiful and useful as rails for the UI... But hey, a man is entitled to dreams :-)