Comment on 70% of new NPM packages in last 6 months were spamparentComments−lolinder2yWhich, incidentally, some people seem to have forgotten when suggesting that NPM should start deleting things en masse.−pdimitar2yWhat other outcome than "curation" do you see as a solution of the "bloat" problem?−3np2yOne possible outcome: Start considering it a public namespace (which in practice it's been not far from for a long time).Meaning curation falls outside it and should not be centrally and unilaterally enforced by gating the entry.We seem to be handling the bloated .com DNS namespace just fine.−pdimitar2yWe seem to be handling the bloated .com DNS namespace just fine.If you say so. I wouldn't think that.−dgfitz2yA new npm-esque?−pdimitar2yMeaning what exactly, sorry?
Comments
Which, incidentally, some people seem to have forgotten when suggesting that NPM should start deleting things en masse.
What other outcome than "curation" do you see as a solution of the "bloat" problem?
One possible outcome: Start considering it a public namespace (which in practice it's been not far from for a long time).
Meaning curation falls outside it and should not be centrally and unilaterally enforced by gating the entry.
We seem to be handling the bloated .com DNS namespace just fine.
If you say so. I wouldn't think that.
A new npm-esque?
Meaning what exactly, sorry?