As much as I want to put this in StackOverflow, I think this particular question fits better here.
I hope this doesn't sound too mean, but this is something that has always bothered me.
I've always wondered why designers / developers of programming language websites don't just put version managers right next to the initial setup and installation instructions in their documentation instead of a long time later, and sometimes they're quite hidden in the side notes.
Most people (I suppose at least) follow the installation procedures line by line. That being the case, and the fact that you usually have to install the version managers first if you need them; Wouldn't it be more logical to inform version administrators about the same point in the documentation as the language installation instructions?
In fact, Ruby is the only language I have installed that started the installation section with something like:
"some language" Installation options:
- Standalone Installation Instructions
- Virtual machine installation
- Installation with a version manager
Then, as stupid as it may seem, I have begun to wonder if there is no reason for this. Obviously, I'm not trying to apologize to anyone for not thinking about version management in advance, however, considering that I almost always forget about version management when I get to a new language, I guess at least it's common Do that Error.
So, is this one of those common misconception things worldwide? Is this even a bad design or am I just crying? Or is there a legitimate reasoning behind this, and if so, what? It seems too common a practice to be just by accident. I mean, who writes the installation procedures, then adds version management instructions at the end and doesn't think, "hey, maybe I should put this on top." ?