News for hackers. Stuff that matters.
Re:Changes to Npm's unpublish policy by imron on Tuesday March 29, 2016 @10:15PM (#11386511)
I've always found it to be a pretty sane scheme. What problems do you have with it?
Re:Changes to Npm's unpublish policy by Cheezykins on Wednesday March 30, 2016 @04:41AM (#11387827)
It feels to me like it's tying your code to something ephemeral. If you're going to do that you may as well make it something uniquely ephemeral. Github, Docker Hub, Packagist et al use usernames for this, it works nicely, packages are namespaced in the form username/packagename.

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.

Re:Changes to Npm's unpublish policy by darkstar999 on Tuesday March 29, 2016 @11:09PM (#11386694)
Coupling it to a TLD is arbitrary. Does Sandra own sandra.com? What if she doesn't have a website at all? It's kind of a silly convention.
Re:Changes to Npm's unpublish policy by qopp on Wednesday March 30, 2016 @01:38AM (#11387182)
This is uncommon, but in this case you can use your email address or github.io, etc.
Re:Changes to Npm's unpublish policy by TeMPOraL on Wednesday March 30, 2016 @02:45AM (#11387394)
It's more common than not to not have a domain. Most programmers I know don't have a personal domain they own, and not all code is written for work (most open-source code isn't, in particular).
Re:Changes to Npm's unpublish policy by tokenizerrr on Wednesday March 30, 2016 @03:59AM (#11387629)
So put your open-source code on github and use something like <githubUserName>.github.io. And if it's for work you use your work groupId. If it's personal but not public, who cares what groupId you use? Just pick something.

What's the problem?

Re:Changes to Npm's unpublish policy by TeMPOraL on Wednesday March 30, 2016 @04:14AM (#11387705)
And when you move your code off github or change your username, are you supposed to change the package name too?

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?

Re:Changes to Npm's unpublish policy by GFK_of_xmaspast on Tuesday March 29, 2016 @11:36PM (#11386793)
You can get a free domain name without a lot of trouble.
Re:Changes to Npm's unpublish policy by gcb0 on Wednesday March 30, 2016 @01:38AM (#11387181)
no you can't.

at most you can borrow one.

Re:Changes to Npm's unpublish policy by ajmurmann on Wednesday March 30, 2016 @01:34AM (#11387171)
I have a bunch of domains, but none of them feel appropriate to use for this. So I might get one just do that I can have a proper package name. Now I have to keep that domain forever. I don't see how this is any different than namespacing by my home address.