News for hackers. Stuff that matters.
Re:Changes to Npm's unpublish policy by awjr on Tuesday March 29, 2016 @06:07PM (#11385326)
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.

Re:Changes to Npm's unpublish policy by steveklabnik on Tuesday March 29, 2016 @06:14PM (#11385371)
npm literally supports namespaces already https://docs.npmjs.com/misc/scope

And, it's not actually clear that a namespace would have been enough had a lawsuit actually been filed.

Re:Changes to Npm's unpublish policy by deckar01 on Tuesday March 29, 2016 @07:07PM (#11385701)
Namespacing costs $7/mo/dev... for a string and a slash.
Re:Changes to Npm's unpublish policy by steveklabnik on Tuesday March 29, 2016 @07:12PM (#11385727)
Not for public ones. Those are free. If you want them to be private, then you pay the money.
Re:Changes to Npm's unpublish policy by awjr on Tuesday March 29, 2016 @06:57PM (#11385651)
scopes are ways of grouping functionally related packages. Not sure that is the same thing.

You may be right about the lawsuit.

Re:Changes to Npm's unpublish policy by igravious on Wednesday March 30, 2016 @12:40AM (#11387018)
By the identity function a package is functionally related it itself and so can be scoped.

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.

Re:Changes to Npm's unpublish policy by tuxracer on Tuesday March 29, 2016 @07:48PM (#11385904)
thought it only figuratively supported namespaces
Re:Changes to Npm's unpublish policy by steveklabnik on Tuesday March 29, 2016 @08:22PM (#11386088)
Literally literally means both nowadays. Language is mutable. Furthermore, I'm using it for emphasis here...
Re:Changes to Npm's unpublish policy by imron on Tuesday March 29, 2016 @10:13PM (#11386505)
Not just nowadays, it's literally had that meaning for hundreds of years: http://blog.dictionary.com/literally/
Re:Changes to Npm's unpublish policy by plaguuuuuu on Tuesday March 29, 2016 @07:12PM (#11385725)
do we really need TLDs in namespaces

it's almost as bad as putting HTTP protocol in XML namespaces.

Re:Changes to Npm's unpublish policy by GFK_of_xmaspast on Tuesday March 29, 2016 @07:26PM (#11385801)
Works ok for java?
Re:Changes to Npm's unpublish policy by Wevah on Tuesday March 29, 2016 @07:53PM (#11385928)
And OS X/iOS app identifiers, etc.
Re:Changes to Npm's unpublish policy by recursive on Tuesday March 29, 2016 @08:51PM (#11386197)
Yes, it works ok. But there are plenty of schemes that both work and are sane.
Re:Changes to Npm's unpublish policy by manyxcxi on Tuesday March 29, 2016 @10:07PM (#11386473)
How is TLD namespacing not sane? If you own the domain you own the package(s) in that namespace. It's pretty easy and fairly trustworthy to identify a TLD. When Stickman Co comes along, there's not a fight about the package name and the original package maintainer doesn't get elbowed out of the way.
Re:Changes to Npm's unpublish policy by TeMPOraL on Wednesday March 30, 2016 @02:44AM (#11387391)
Domain names are transient. They come and go, changing owners throughout their lifetime. Code, on the other hand, lives on.

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.

Re:Changes to Npm's unpublish policy by jasonkostempski on Wednesday March 30, 2016 @12:20AM (#11386946)
I'm pretty sure domains have been transferred to their "rightful owner" even more than NPM package names have.
Re:Changes to Npm's unpublish policy by erik14th on Wednesday March 30, 2016 @12:52AM (#11387046)
I think TLD is ok, but I like Go's namespacing even better. It uses repos, so you can use both private and public repos. And it's actually where the code "live".
Re:Changes to Npm's unpublish policy by sha90 on Wednesday March 30, 2016 @05:28PM (#11393174)
Git repos change way more often than domain or company names do. Moving from code.google.com to github.com, moving a project from a user to an org, transferring across orgs, renaming an org. All of these things have happened to me in a single Golang project. Ironically, the code.google.com -> github move was actually Golang stdlib code itself.
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.
Re:Changes to Npm's unpublish policy by walterstucco on Wednesday March 30, 2016 @11:15AM (#11389864)
NO!
Re:Changes to Npm's unpublish policy by paulhodge on Tuesday March 29, 2016 @10:14PM (#11386507)
Dots are allowed in the package name, so there's nothing stopping someone from having a package named "com.sandra.stickman", if they are really inclined to do that.
Re:Changes to Npm's unpublish policy by TheDong on Tuesday March 29, 2016 @10:41PM (#11386612)
You're missing the point. Being intentionally obtuse adds nothing.
Re:Changes to Npm's unpublish policy by paulhodge on Thursday March 31, 2016 @12:06AM (#11394919)
If I was being obtuse then it was unintentional. It was a real suggestion. If people really want reverse TLD names then they should do it, and if the community likes it, it will catch on. FYI there are already some package names out there with ".com" on the end.
Re:Changes to Npm's unpublish policy by woah on Wednesday March 30, 2016 @12:42AM (#11387022)
That's why it's best not to force people to namespace with backwards website addresses.