Though I don't have much to articulate, more of a feeling, really, I felt compelled to respond to Raiding Rails' statement that "Rails Has Great Documentation." I'm by no means an experienced Rails developer - I've written a few small applications, even a simple gem - but as someone who's only recently learned enough of the framework to find his way around, I'd like to state simply that I found the process more frustrating from a documentation standpoint than previous learning experiences. I won't argue with any of the points that Gregg makes in his post. For the most part I find them completely valid, with Ryan Bates' Railscasts.com playing a particularly important role in my own education, but that doesn't change my own experience. Maybe it's stylistic choices within the resources themselves (I've found them to be quite narrative) or perhaps the organization of the community around them, I honestly don't know. With how amorphous these statements are, I'm not advocating, or ready to propose, a change. What I would like to do is share my experience, as vague as it may be, and hope that people with much more Ruby on Rails knowledge and involvement, like Gregg, will take notice and help bridge the gap for novice developers struggling with the documentation, like myself.
Comparisons of Ruby vs Javascript. A great primer if you're familiar with one of the languages but not the other.
If I could borrow a perspective for the moment, I'd borrow _why's.