Programming Ruby: A pragmatic programmer's guide (first edition)
First time to learn RubyonRails
Originally posted by Mark Ju:
If you want to learn Rails, I suggest not using those bundled installers, such as Instant rails. Install the pieces for yourself -- you'll know better what's going on under the hood. The downside, of course, is that if it messes up your system, it's harder to back out.
Doesn't that kind of contradict what Rails is about and it's philosophy? Is that different than saying:
"If you really want to learn rails don't use any of the scaffolding or code generation. Write it all by hand. That way you really know what's going on under the hood"
And if you say that, then there really is no argument to use Rails.
For me, the line is drawn at my environment setup: I like Rails, my db, my server, etc not be too tightly coupled. Why? Because when I deploy, upgrade, downgrade, optimize, or otherwise tinker with one piece, I can do so without affecting the other parts.
On the other hand, one major selling point of Rails is its tightly coupled MVC stack. It's proven, actively maintained, and a joy to work with. I wouldn't want to switch out ActiveRecord with my own ORM (though I think others have done that).
I don't know any commercial apps in production entirely based on Instant Rails/Locomotive. That's all I was trying to get at.
Whether or not Rails is proven compared to other languages or frameworks, I'm not sure, but it does the job for my projects and so far, I'm enjoying it.