On: Trouble in Node.js paradise: The mess that is npm

[modeless]

Duplication of effort is a non-problem, and any attempt to "fix" it would reduce contributions and discourage innovation. With good metrics the best solutions will rise to the top over time.

[astrodust → modeless]

The problem is metrics. How is this problem addressed?

Ruby and Python seem to suffer the same problem with a lack of feedback on the quality of offerings.

[wycats → astrodust]

In Ruby, the Ruby Toolbox does a good job of providing reasonable, automatable metrics. https://www.ruby-toolbox.com/

[mikl → modeless]

I'd say every minuted wasted reinventing the wheel is a minute that was not spent solving interesting problems.

I'm not sure what you're referring to when you talk about fixes that would discourage innovation or contribution. I'd say I suggest the opposite, in fact :)

[dextorious → modeless]

"""Duplication of effort is a non-problem,"""

Really? Because of I've been following OSS communities for, like, 15 years, and it has been a huge problem in most of them.

[malandrew → dextorious]

Duplication of effort leaves more room for experimentation, so it's not all bad.

If there was only one canonical version of all modules, it would be very limiting.

For problems that are deemed solved or community issues, having one or canonical module is great. A good example of this is JSLint and JSHint.

For problems that at TIMTOWTDI, duplication of effort allows exploration of the problem space. Once the right location for the new hive has been found we'll just headbutt the other worker bees into submission :P

[dextorious → malandrew]

I agree -- I was basically answering the parent that it's a "non problem". Sometimes it IS a problem.