News for hackers. Stuff that matters.
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.