If you were logged in, then you could vote. Don't wait. Login and vote now.
By bloid
via weblogs.java.net
Published: Apr 14 2008 / 07:06
The other day one of my team members was complaining about the lack of documentation in Ruby on Rails. I had to think for a minute because I never had problems finding information I needed. It finally occurred to me that the ruby development and documentation cycle is very different than Java's.
Comments
nightwind replied ago:
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.
Tantalus replied ago:
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...
Voters For This Link (7)
Voters Against This Link (5)