From: Aaron Becker Date: 2006-03-07T14:29:08+09:00 Subject: No documentation for modules on RubyForge? Warning: flames ahead... My opinion is Ruby is doomed if it doesn't enforce some type of quality control on modules and general usability. This is especially true for the gotchas new users will face. Why not have a checklist of requirements for accepted modules? I used gem to install "stomp" but there is no documentation and not even a synopsis in the code. Also the module loading error messages from Ruby are wanting. Has anyone analyzed the most likely stumbling blocks for new users? Has anyone done a usability study on new users? There's nothing worse than having potential and then not following through with the fundamentals. Don't expect me to be an expert Ruby programmer if I am new to the language. But even the most level-headed developer would expect that all modules would have documentation. The same goes for 'reliable/msg'. It has no documentation. And it's claimed to be 'stable'??? WTF? Besides Ruby is so powerful, I can't believe that anyone hasn't improved these fundamentals. I've never had this issue with CPAN. Can’t someone write a simple webrick app to navigate the symbols and namespaces at run-time? Shoot, look at the JavaScript and DOM if you need an example of a possible interface: http://www.brainjar.com/dhtml/domviewer/ . And when I used Symbol.all_symbols it wasn’t clear how to get the full namespace of the symbols. Navigating the symbols in Perl is far easier. And where is a cookbook or snippet site for Ruby code? And what about the ability to search Ruby-talk archives? Surely Google could help with that. You can spray a dog turd with gold paint, but it's still a dog turd. Hopefully, you can make Ruby live up to the hype... And soon. hackdaddy -- Posted via http://www.ruby-forum.com/.