← Back to context Comment by pdimitar 2 years ago What other outcome than "curation" do you see as a solution of the "bloat" problem? 4 comments pdimitar Reply 3np 2 years ago 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. pdimitar 2 years ago > We seem to be handling the bloated .com DNS namespace just fine.If you say so. I wouldn't think that. dgfitz 2 years ago A new npm-esque? pdimitar 2 years ago Meaning what exactly, sorry?
3np 2 years ago 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. pdimitar 2 years ago > We seem to be handling the bloated .com DNS namespace just fine.If you say so. I wouldn't think that.
pdimitar 2 years ago > We seem to be handling the bloated .com DNS namespace just fine.If you say so. I wouldn't think that.
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.
> 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?