4 ms·
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
by manyxcxi 11y ago
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.
- jasonkostempski 11y agoI'm pretty sure domains have been transferred to their "rightful owner" even more than NPM package names have.
- erik14th 11y agoI 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".
- sha90 11y agoGit 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.
- TeMPOraL 11y agoDomain 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.