Javascript on suicide watch

archive.fo/2018.01.11-205122/https://github.com/npm/registry/issues/255

Many packages suddenly disappeared

Other urls found in this thread:

twitter.com/maybekatz
twitter.com/ReBeccaOrg
github.com/jonschlinkert/is-number>
lua.org/pil/2.3.html
github.com/jonschlinkert/is-odd>
mobile.twitter.com/izs/status/911105515798720513
redox-os.org/
twitter.com/SFWRedditVideos

Is this the power of Specdown?

...

Not the first time this happened, there was a widescale issue due to the same reason (dev of a very popular package killed their repo because of drama or some shit, every site using the library, which was a lot of them, became outright unusable for a week or so).
Or is it the same one?

...

That almost makes me want to become a nodejs developer just to make and subsequently memory-hole a highly depended package.

this

I have no fucking idea how node ever got popular considering it's easily the worst thing ever.

There is nothing wrong with node itself, you just have to stop being a fucking nigger and downloading libraries instead of writing code yourself.

Except for the fact that it uses javascript