Link Details

Wow, someone complains about a lack of RoR documentation and his answer is "First of all, ruby code *is* documentation"?
I call BS. RoR is all about convention, magic and pixie dust. That's all nice and dandy, but you need to know what the conventions *are*.
Unless you have a nice documentation and lot of experience RoR is just a "WTF?" waiting to happen. You cannot have the cake and eat it. Either you have documentation, clear concepts and coding by convention, or you have it the java style, self-documenting, very verbose code that forces you to spell it all out.

Agreed. When I first started looking at Rails, you had the Pragmatic book or you were right screwed unless you already knew a lot of Ruby, but of course, I only wanted to know Ruby to use Rails...