8 ms·
That's the sensible behavior if you plan on reading local documentation. I can't say I've ever used ri, although I do browse local rdoc, sometimes. I know plen
by generalk 16y ago
That's the sensible behavior if you plan on reading local documentation.
I can't say I've ever used ri, although I do browse local rdoc, sometimes. I know plenty of developers that hadn't heard of "gem server" until I mentioned it. And this is completely discounting production environments, where the documentation is almost certainly a waste of deploy time.
- geeksam 16y agoI hadn't heard of "gem server" until you mentioned it.
- rue 16y agoApproximately 60% of all questions on #ruby-lang could have been answered by ri, just for the core and stdlib. It's a shame it doesn't get used more. It's an orthogonal problem, though. The main issue with doc generation is that it is really, really slow (compared to the rest of the install process). If it can be sped up – patches are surely welcome – it'll just leave the envs that flat-out don't need the docs, ever, and those can use the new --no-doc.