3 ms·
My experience with Rails is that if you stay on the path it marks for you, you will really develop on rails. If you want to customize a little, it makes it real
by pestaa 16y ago
My experience with Rails is that if you stay on the path it marks for you, you will really develop on rails. If you want to customize a little, it makes it really painful.
If all you need is a CRUD app such as Basecamp and the other products from 37signals, Rails is a no-brainer and you'll be already half-way done.
If you need something more or something different, you better off looking deep in the pool of plugins, because if they don't have the answers, you'll need many hours to break the convention and tweak to your requirements.
The essay-like queries is a code smell, by the way, and to me it suggests you're underutilizing Active Record scopes.
- mkrecny 16y agoI agree. Based on conversations that I've had with rails gurus (I'm in a co-work space with pivotal labs) the essay-like queries are definitely a code smell. I think the guy who has laid the relational foundation for the app I'm working on (and taught me all the rails I know to date) has done so in a non-Railsy way.
- pestaa 16y agoYes, and it's not Rails only; every framework that uses Active Record (and that covers the vast majority) requires this sort of approach. "Skinny controller, fat model" is not as easy as it sounds.
- frankus 16y agoNot to sound flippant, but there's your first problem. Rails really doesn't want to be layered over an legacy database schema. Doing so would definitely lead to essay-like queries.