The real problem is the namespace issue that seriously needs sorting out. com.sandra.stickman would be different to com.stickmanufacturingcorp.stickman
npm is growing hugely. It needs to sort out the domain space issue quickly.
npm is growing hugely. It needs to sort out the domain space issue quickly.
And, it's not actually clear that a namespace would have been enough had a lawsuit actually been filed.
You may be right about the lawsuit.
I am not sure if I am being playful or not. I'll edit this post if I figure it out before the hour's grace period is up.
it's almost as bad as putting HTTP protocol in XML namespaces.
If you want namespacing to be tied to Internet domains then I want the right to take over your code after you forget to renew your domain.
People advocating using a domain as the namespace get the same result, but the package namespace is tied to a domain, you have to have control of that domain, if you lose it, do you lose the namespace?
What if I don't own any domain, people are saying in that instance I should use io.github.myusername, why not just myusername? that way my code isn't tied to a platform I may not use in 5 years time.
I suppose that's it, a namespace is about my code, not about where the code is maintained or an external resource I may or may not keep access to, so don't namespace it in a way that ties it to such.
What's the problem?
If not, or if we're going to put whatever we want in there anyway, then why hold to the idea it must correspond to a domain name anyway?
at most you can borrow one.