Ruby on Rails

On Apr 26, 2012, at 1:36 AM, Michael Pavling wrote:

> Again.... *which* bit of documentation needs to be better... how many
> times have you honestly been confounded by not finding something in
> the docs? (and when you did, did you contribute to fill the hole?)

Nearly every frickin' time I look something up. Rails docs are really awful compared to every other framework I've ever used. You ask for specific examples, but in this case that's almost a misdirection. Documentation of methods should cover *every* argument and option, and they just do not. The guides are pretty good; the references stink.

And I like RoR. And I'll say what you're all thinking: it's clear that the guy ranting about how you can't get anything done just didn't grok something and must not have bothered with any of the fine introductory books, because his claims are just not true. And no, RoR will not be gone in 5 years. At the time it came out it was a far better way to develop way apps, and it certainly has kept up.

But the reference docs are woefully inadequate, and this is a huge barrier to people trying to move from beginner to mastery.

--
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice




--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.