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 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 ]