That's the part that really got me. Questionable dependency practices is one thing; but running whatever JS when a package is installed, with no warning whatsoever, is probably a very bad idea.
A year ago I never ever would've thought I'd be happier writing C than NodeJS, but here I am. Weird how that works.
It destroys days of development.
> This is the sort of amateur behaviour that is emblematic of the entire nodejs community.
This is pure mudslinging
https://www.reddit.com/r/rust/comments/4bm3rk/how_would_crat...
That's a strange thing to say considering how insanely complex modern hardware and software are. While the NPM setup is indefensible, there are countless ways a stranger can prevent your deployment, if that stranger works at Microsoft, Intel, or the manufacturer of any production hardware component. OS bugs, driver bugs, compiler bugs, and hardware/microprocessor bugs are a thing. At any point, you are dependent on the work of many thousands of strangers, no matter how perfect your decisions are.