5 ms·
The real problem is the namespace issue that seriously needs sorting out. com.sandra.stickman would be different to com.stickmanufacturingcorp.stickman npm is
by awjr 11y ago
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.
- paulhodge 11y agoDots 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.
- TheDong 11y agoYou're missing the point. Being intentionally obtuse adds nothing.
- woah 11y agoThat's why it's best not to force people to namespace with backwards website addresses.
- paulhodge 11y agoIf 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.
- steveklabnik 11y agonpm literally supports namespaces already https://docs.npmjs.com/misc/scope 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.
- awjr 11y agoscopes are ways of grouping functionally related packages. Not sure that is the same thing. You may be right about the lawsuit.
- igravious 11y agoBy 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.
- deckar01 11y agoNamespacing costs $7/mo/dev... for a string and a slash.
- steveklabnik 11y agoNot for public ones. Those are free. If you want them to be private, then you pay the money.
- tuxracer 11y agothought it only figuratively supported namespaces
- steveklabnik 11y agoLiterally literally means both nowadays. Language is mutable. Furthermore, I'm using it for emphasis here...
- imron 11y agoNot just nowadays, it's literally had that meaning for hundreds of years: http://blog.dictionary.com/literally/ http://blog.dictionary.com/literally/
- plaguuuuuu 11y agodo we really need TLDs in namespaces it's almost as bad as putting HTTP protocol in XML namespaces.
- deleted 11y ago[deleted]
- GFK_of_xmaspast 11y agoWorks ok for java?
- recursive 11y agoYes, it works ok. But there are plenty of schemes that both work and are sane.
- manyxcxi 11y agoHow 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.