One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
I wonder whether npm makes it too easy to publish a package.
In the Java world, publishing something to mavenCentral is confusing and painful ; as a result it raises the bar to which projects are motivated enough to publish something.
Absolutely. And, to an extent, workflows (used to) promote publishing your own packages for ease of access. Separate something out of your code? Why not push it straight to npm?
Curation is necessary in many ways, and hosting your own package repository is a bar usually not taken unless you reach a certain size. This has gotten better, particularly with more sensible defaults and different workflows (node generators have helped hugely), but we still see the impact.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I wonder whether npm makes it too easy to publish a package.
In the Java world, publishing something to mavenCentral is confusing and painful ; as a result it raises the bar to which projects are motivated enough to publish something.
Absolutely. And, to an extent, workflows (used to) promote publishing your own packages for ease of access. Separate something out of your code? Why not push it straight to npm?
Curation is necessary in many ways, and hosting your own package repository is a bar usually not taken unless you reach a certain size. This has gotten better, particularly with more sensible defaults and different workflows (node generators have helped hugely), but we still see the impact.