507

What could possibly go wrong (sh.itjust.works)

submitted 1 year ago by alphacyberranger@sh.itjust.works to c/programmer_humor@programming.dev

13 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] v1605@lemmy.world 33 points 1 year ago

https://qz.com/646467/how-one-programmer-broke-the-internet-by-deleting-a-tiny-piece-of-code

[-] Feirdro@lemmy.world 10 points 1 year ago

This was excellent, but conveniently left off any discussion that npm can “un-un-publish” a programmer’s code against their wishes, and apparently without repercussions?

Fuck npm, I guess.

[-] mexicancartel@lemmy.dbzer0.com 13 points 1 year ago

Absolutely they can un-unpublish since the programmer has given everyone the rights to use his code wherever they want, with its open license. Npm can actually use the older version of the code and give it to everyone. Its actually a good thing

[-] Feirdro@lemmy.world 6 points 1 year ago

Right, the “open” part of open source.

[-] DarkenLM@kbin.social 3 points 1 year ago

Thank fuck for that, cause if they didn't faker.js and node-ipc would have caused a lot of trouble, with the developers adding malware to a new version and later deleting the entire packages, breaking tons of projects. And those were everything but small packages.

[-] Anonymousllama@lemmy.world 2 points 1 year ago

All for the greater good, especially if it's the choice between one guy's desire to nuke their own code VS tens / hundreds of thousands of projects that depend on it.