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