Disabling npm's progress bar yields a 2x npm install speed improvement

Re:Disabling npm's progress bar yields a 2x npm install spee... by gavinjoyce on Tuesday January 26, 2016 @03:47PM (#10975932)

Some further details on the issue: https://github.com/npm/npm/issues/11283

[ Parent | on HN ]

Re:Disabling npm's progress bar yields a 2x npm install spee... by deelowe on Tuesday January 26, 2016 @05:07PM (#10976542)

Now that's what I call a bug report: https://github.com/npm/npm/issues/11283#issuecomment-1752468...

[ Parent | on HN ]

Re:Disabling npm's progress bar yields a 2x npm install spee... by gkya on Wednesday January 27, 2016 @06:37AM (#10979520)

That's what I call a slideshow.

[ Parent | on HN ]

Re:Disabling npm's progress bar yields a 2x npm install spee... by VeilEm on Tuesday January 26, 2016 @04:17PM (#10976147)

Please refrain from adding unhelpful comments to the issue.

[ Parent | on HN ]

Re:Disabling npm's progress bar yields a 2x npm install spee... by eric_h on Tuesday January 26, 2016 @04:32PM (#10976272)

It is tremendously unfortunate that that needs to be said at all.

[ Parent | on HN ]

Re:Disabling npm's progress bar yields a 2x npm install spee... by skissane on Tuesday January 26, 2016 @06:54PM (#10977198)

I think bug tracker comment forms for open source projects need some kind of question first (at least from people who aren't active contributors), like "Please select your type of comment":

* Nontechnical: I would like to express my eagerness that the bug be fixed or request its priority be increased, but don't have any additional technical information to add

* Technical: I have useful technical information to add, beyond what is already in the bug

Then "Nontechnical" type comments would be hidden from the developers by default (unless they specifically ask to see them), but their count could be used as a bug prioritisation mechanism (effectively leaving a "Nontechnical" type comment would be counted the same as a vote)

[ Parent | on HN ]

Re:Disabling npm's progress bar yields a 2x npm install spee... by voltagex_ on Tuesday January 26, 2016 @06:34PM (#10977105)

I guess it's GitHub's Eternal September. I'm all for more people having access to development tools, but GitHub really has to step up the tools available for managing issues/comments.

[ Parent | on HN ]

Re:Disabling npm's progress bar yields a 2x npm install spee... by bostonvaulter2 on Tuesday January 26, 2016 @07:09PM (#10977274)

There is this open letter to github from open source maintainers: https://github.com/dear-github/dear-github

[ Parent | on HN ]

Re:Disabling npm's progress bar yields a 2x npm install spee... by striking on Tuesday January 26, 2016 @04:51PM (#10976411)

How is this unhelpful exactly? It's a link to another discussion that readers might be interested in.

[ Parent | on HN ]

Re:Disabling npm's progress bar yields a 2x npm install spee... by X-Istence on Tuesday January 26, 2016 @04:54PM (#10976432)

Op was stating you shouldn't follow that link and go "Hey, me too" or "+1" on the Github Issue.

Not that the link to the issue was unhelpful.

[ Parent | on HN ]

Re:Disabling npm's progress bar yields a 2x npm install spee... by baudehlo on Tuesday January 26, 2016 @09:09PM (#10977753)

GitHub badly needs an "approve" system that is external to comments, like bitbucket has.

[ Parent | on HN ]

Re:Disabling npm's progress bar yields a 2x npm install spee... by striking on Tuesday January 26, 2016 @11:34PM (#10978234)

Because I can't amend this comment:

I misunderstood the commenter above me. My sincerest apologies. Have a nice day!

[ Parent | on HN ]

Re:Disabling npm's progress bar yields a 2x npm install spee... by l1ambda on Tuesday January 26, 2016 @09:26PM (#10977811)

[ Parent | on HN ]