Here are some normally hidden yet very useful rake tasks. Why hidden? Because they’re not documented. And rake hides undocumented tasks by default.
Python has wonderful things like docstrings and help(), as well as a community that values documentation so much they actually write it. Write documentation? Willingly? Crazy, I know, but it really spoils you.
The Ruby 2.1 release notes … didn’t go too much into detail. To find out more, you are pretty much left with diving through the Ruby issue tracker.
A page full of irrelevant ads and links to deprecated software. That’s what you get when you search in the official Ruby API.
The official Rails site points here for the core dev discussion. But the group is moribund: half the posts have no reply. Very low traffic. I couldn’t find any posts by core devs.
Is core dev conversation held in private only? Have I missed something?
My rageful Ruby/Rails realization of the day:
- Create a new Rails app
- Follow the link to documentation
- Get a 404.
Bonus annoyance points for (a) this being an API page, (b) the lack of creating a redirect, and (c) the implied lack of caring and respect for app developers.
The new Ruby 2 “named parameter” feature … isn’t documented
— My rageful Ruby/Rails realization of the day
Getting fed up with the state of Ruby and Rails documentation
As long as I’ve known about Python, there’s been;
- a canonical home page (python.org), with
- one single easy-to-see Documentation nav link. And finally,
- at the top of the Documentation page, there are two docs that answer 99% of questions about the language: Tutorial (which is really a complete language guide), and Library Reference.
There isn’t a comparable doc for ruby.