4 ms·
Nope, nothing wrong. The code he wrote is his, but he doesn't own the npm namespace, which is all anyone cares about here at this point. But you know what also
by swang 11y ago
Nope, nothing wrong. The code he wrote is his, but he doesn't own the npm namespace, which is all anyone cares about here at this point.
But you know what also _feels_ wrong? people who had no involvement in this at all having their day get fucked up because of this one dude who _suddenly_, just now realized that npm isn't going to really help him out and did the internet equivalent of taking your ball and going home.
- spdustin 11y agoAgreed, that feels wrong too. But is npm supposed to be the recess supervisor in this metaphor, taking the ball back and giving it back to the other kids?
- alextgordon 11y agoIf he wants to control where people get his software, he should have published it under a proprietary license. Not saying he does, though.
- spdustin 11y agoFair enough. I would posit that he didn't ever expect that the npm folks would undo his actions, even if his decisions were/seemed rash.
- swang 11y agoHe doesn't care if anyone takes over the leftpad module. He unpublished leftpad Someone else republishes leftpad as a new owner Since npm won't allow you to publish old versions, stuff is still broken since the depended on files have a hard dependency on v0.0.3 npm (the company) forces a republish on v0.0.3 or I guess an ununpublish.