4 ms·
IIRC, it was npm (not node) that rolled over and gave it to kik just because they felt like it would be "confusing." http://blog.npmjs.org/post/141577284765/ki
by chickenfries 9y ago
IIRC, it was npm (not node) that rolled over and gave it to kik just because they felt like it would be "confusing."
http://blog.npmjs.org/post/141577284765/kik-left-pad-and-npm http://blog.npmjs.org/post/141577284765/kik-left-pad-and-npm
https://medium.com/@mproberts/a-discussion-about-the-breaking-of-the-internet-3d4d2a83aa4d https://medium.com/@mproberts/a-discussion-about-the-breakin...
- deletia 9y agoThis ^ Arguably one of the best things to come out of that whole incident was NPM's realization that the (then) entire system of dependencies had a huge issue; that is, the fact that one pissed of developer could break a massive amount of production codebases. IMHO the incident was a good learning experience for the JS community as a whole and really shouldn't be framed so negatively all the time.
- chickenfries 9y agoI think a lot of it was much ado over nothing, but I agree that if you didn't already mistrust tiny, anemic modules written by single developers in your production code that it was a good lesson.
- deletia 9y agoExactly :) A lot of larger companies affected needed a wake up call regardless.
- pooper 9y agoThe issue to me isn't the deletion of modules but rather the reassignment of modules. I'm completely ok with deleting modules. I am not ok with taking a name that used to exist and just giving it to someone else. That is the crime here not the deletion of modules. That should be the wake up call.