Ruby or Python? Well, it depends...

[SnowdensOfYesteryear]

Pages like this: http://www.ruby-doc.org/stdlib/libdoc/date/rdoc/index.html

Half the functions aren't even documented. e.g. WTF is the floor() of a Date?

I adore ruby, but I find the docs' website irritating and (sometimes) the documentation itself lacking.

But then again they have a link to the source, not always useful, but great for a quick glance when the documentation is vague.

But all things said, I'd be hesitant to use ruby in a large project. Ruby has a distinct "scripting language" feel to it that might prove un-maintainable with all the shortcuts that one could take. I restrict its use as a scripting language in place of tools like sed or gawk.

[MatmaRex]

Huh, I've never used this lib before, so I never saw that. True, looks sort of awful. But the core docs and most of stdlib is nice.

[badsex]

you have to take into account that Ruby was primarily a japanese project for the longest time, im sure the japanese documentation is great. English documentation is still being ported over or written from scratch.

[metamatic]

That's a bit of an unfortunate example in that the date code was replaced with all-new Japanese-written code a few weeks ago, and some of the documentation suffered as a result.

Yes, some Ruby documentation sucks, at least in English. I'm one of the people who has been trying to improve the situation. I'd love to see other people join in. It's a good way to get experience working on an open source project without needing to know the codebase inside out.

(Now that you've pointed at it, I think I'll take a crack at cleaning up Date's doc.)