Comment Re:i think you answered your own question (Score 2, Insightful) 295
In other words: The implicit assumption in the original question is incorrect: These frameworks are *not* concentrated merely on getting apps running quickly.
Of course the infamous manner of showing off these frameworks is to make a screencast showing how easy it is to make a simple wiki or todo list. These screencasts can be misleading since they often employ simple CRUD scaffolding, which is useless in the real world. However, taken with a grain of salt, they help you get a feel for the framework.
A good MVC framework helps organize your code in a standard manner, and a you get a lot of mileage from leveraging a supported, tighly integrated, full stack like that of Ruby on Rails. (It's really fantastic: handles everything from ORM to script.aculo.us with blissful ease.)
Pardon my fanaticism, but I decided to learn Ruby on Rails last weekend, and I'm quite certain it'll be the main thing I'll be coding my own projects from now on. (Catalyst looks good if you don't wish to abandon good old Perl.)
Of course the infamous manner of showing off these frameworks is to make a screencast showing how easy it is to make a simple wiki or todo list. These screencasts can be misleading since they often employ simple CRUD scaffolding, which is useless in the real world. However, taken with a grain of salt, they help you get a feel for the framework.
A good MVC framework helps organize your code in a standard manner, and a you get a lot of mileage from leveraging a supported, tighly integrated, full stack like that of Ruby on Rails. (It's really fantastic: handles everything from ORM to script.aculo.us with blissful ease.)
Pardon my fanaticism, but I decided to learn Ruby on Rails last weekend, and I'm quite certain it'll be the main thing I'll be coding my own projects from now on. (Catalyst looks good if you don't wish to abandon good old Perl.)
