4 ms·
> So you're saying the root problem is you haven't configured your production servers? I'm not sure what you mean. If you mean "It's trivial to add 'gem: --no-
by telemachos 16y ago
> So you're saying the root problem is you haven't configured your production servers?
I'm not sure what you mean. If you mean "It's trivial to add 'gem: --no-ri --no-rdoc' to your .gemrc file. It's your fault if you haven't configured your server correctly.", then you're avoiding the point of this argument.
We all agree that you can change defaults. We're discussing what the default should be.
- technomancy 16y agoThe default should be what makes sense in a development environment, since rubygems is a development tool. The fact that you can use it to perform deployments as well is interesting, but doesn't concern this question. Generating both HTML and console documentation is suspect, but generating no documentation at all is much worse.
- nirvdrum 16y agoCould you elaborate a bit please? I've read your comment a few times over and I don't quite get what you mean that it's a "development tool." I have no idea what you mean by using it "to perform deployments." To me, and everyone I did a very quick straw poll of, rubygems is a loader for gem files. If it's truly only meant to be a dev tool, what would you suggest instead for loading third party libraries into an app?