Heres a nice Ruby (Not Ruby on Rails) to get you started on the fundamentals of Ruby. It helps to get to know the syntax and the way the language works later on when trying to figure out why things aren't working they way you planned, etc.
The book Ruby for Rails is also a very good for beginning RoR. I've been reading it and it has really helped me understand some of the details of how Rails works and how to take advantage of Ruby for use in web app development.
Joined: Jul 20, 2005
Ruby on Rails Up and Running is another decent book. It's only 150 some pages so it doesn't go into great detail. But, it does a decent job of introducing Ruby on Rails.
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.
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.
No, I'm not saying don't use scaffolding. But it's true you'll have a firmer grip on things if you don't. You'll have to decide for yourself where to draw the line between convenience and control.
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).