5 ms·

From drbrain in the comments: 1.7 will replace --no-rdoc and --no-ri with a single --[no-]document option (which should be automatically aliased to --[no-]doc

by wlll 16y ago

From drbrain in the comments: 1.7 will replace --no-rdoc and --no-ri with a single --[no-]document option (which should be automatically aliased to --[no-]doc by optparse) making this easier to do. Not quite the same, if that was what was meant, and calling people who express a valid opinion on this "propellerheads" just seems unnecessarily insulting. There are 200+ comments because people feel strongly about this and not because they are trolling.

steveklabnik 16y ago
I also think that it's a bit excessive. Some people seem to get frothy at the mouth when they see 'dhh.'
- deleted 16y ago
  [deleted]
rst 16y ago
But he's directly refusing to make --no-doc the default, which is the whole point of the request. People are complaining about having to install a .gemrc to get sensible behavior. Making the file a few characters shorter doesn't make it less of a burden.
- xiaomai 16y ago
  The sensible behavior is to install the documentation., so no .gemrc is necessary (to get sensible behavior).
  - steveklabnik 16y ago
    That's the entire point of this discussion. A large body of Rubyists think that the sensible behavior is to _not_ install the documentation. I google far more often than I ri.
    - mcantor 16y ago
      Maybe the real problem is that Ruby documentation generally sucks! :-)
      - steveklabnik 16y ago
        At least there are tests to make up for it. ;)
  - 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 ago
      I hadn't heard of "gem server" until you mentioned it.
    - rue 16y ago
      Approximately 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.
  - bronson 16y ago
    The vast majority of gemrcs on github disagree with you: http://www.google.com/search?hl=en&source=hp&biw=1012&bih=945&q=gemrc+site:github.com&aq=f&aqi=&aql=&oq= http://www.google.com/search?hl=en&source=hp&biw=101... Personally, I can switch to a browser window, google for a gem, find its docs, and read them online in less time than it takes for ri to return its usually incomplete result or ask for brain-dead disambiguation. Ruby would have a better reputation if ri simply didn't exist.
bschaefer 16y ago
...calling people who express a valid opinion on this "propellerheads" just seems unnecessarily insulting When did "+1" become a valid opinion? The few people who attempted to actually discuss the patch were more than drowned out by -- well -- a bunch of propellerheads.
- wlll 16y ago
  It's shorthand for agreeing with the original idea. It saves space and allows a much quicker scanning of the comments to find people who have something unique to say. If everyone wrote a short paragraph on their agreement with the original idea it would be very hard to find the comments where people were either dissenting or had something original to say.
  - Dylan16807 16y ago
    Is this a flaw in github? It has this nice compact list of people at the top; there's no way to join it without spamming a comment?
    - xiaomai 16y ago
      I like launchpad's "This bug also affects me" link. Maybe github could implement something similar.
    - steveklabnik 16y ago
      I'd say it's a sensible default that happens to be broken in this case. ;)
    - matthewcford 16y ago
      they just need up-votes - effectively a plus 1
nirvdrum 16y ago
I've found most of the comments on just about anything from the RubyGems guys to be off-putting, degrading, and/or insulting. Not to mention just about every new release breaks my apps on me and it's always made out to be my fault (or someone else's, but never the fault of RubyGems). It is probably my least favorite aspect of using Ruby and being part of the "community."

by wlll 16y ago

steveklabnik 16y ago

I also think that it's a bit excessive. Some people seem to get frothy at the mouth when they see 'dhh.'

deleted 16y ago
[deleted]

rst 16y ago

But he's directly refusing to make --no-doc the default, which is the whole point of the request. People are complaining about having to install a .gemrc to get sensible behavior. Making the file a few characters shorter doesn't make it less of a burden.

xiaomai 16y ago
The sensible behavior is to install the documentation., so no .gemrc is necessary (to get sensible behavior).
- steveklabnik 16y ago
  That's the entire point of this discussion. A large body of Rubyists think that the sensible behavior is to _not_ install the documentation. I google far more often than I ri.
  - mcantor 16y ago
    Maybe the real problem is that Ruby documentation generally sucks! :-)
    - steveklabnik 16y ago
      At least there are tests to make up for it. ;)
- 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 ago
    I hadn't heard of "gem server" until you mentioned it.
  - rue 16y ago
    Approximately 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.
- bronson 16y ago
  The vast majority of gemrcs on github disagree with you: http://www.google.com/search?hl=en&source=hp&biw=1012&bih=945&q=gemrc+site:github.com&aq=f&aqi=&aql=&oq= http://www.google.com/search?hl=en&source=hp&biw=101... Personally, I can switch to a browser window, google for a gem, find its docs, and read them online in less time than it takes for ri to return its usually incomplete result or ask for brain-dead disambiguation. Ruby would have a better reputation if ri simply didn't exist.

bschaefer 16y ago

...calling people who express a valid opinion on this "propellerheads" just seems unnecessarily insulting When did "+1" become a valid opinion? The few people who attempted to actually discuss the patch were more than drowned out by -- well -- a bunch of propellerheads.

wlll 16y ago
It's shorthand for agreeing with the original idea. It saves space and allows a much quicker scanning of the comments to find people who have something unique to say. If everyone wrote a short paragraph on their agreement with the original idea it would be very hard to find the comments where people were either dissenting or had something original to say.
- Dylan16807 16y ago
  Is this a flaw in github? It has this nice compact list of people at the top; there's no way to join it without spamming a comment?
  - xiaomai 16y ago
    I like launchpad's "This bug also affects me" link. Maybe github could implement something similar.
  - steveklabnik 16y ago
    I'd say it's a sensible default that happens to be broken in this case. ;)
  - matthewcford 16y ago
    they just need up-votes - effectively a plus 1

nirvdrum 16y ago

I've found most of the comments on just about anything from the RubyGems guys to be off-putting, degrading, and/or insulting. Not to mention just about every new release breaks my apps on me and it's always made out to be my fault (or someone else's, but never the fault of RubyGems). It is probably my least favorite aspect of using Ruby and being part of the "community."