| > * package management and modules actually work > * huge ecosystem of packages This is satire, right? NPM (both the tool, and the repository of packages it pulls from) are a joke to anyone outside the NodeJS bubble of Stockholm syndrome. A company that was given $8M in venture capital and can't find more than two people to work on the main way people interact with their service, cannot be taken seriously. Remember when everyone found out that the progress bar made NPM install packages 3x slower? Then lets get into the actual 'ecosystem'. The community actively encourages and embraces the sort of culture and decision making that leads to an entire module to do what you can do with this: `$foo % 2 === 0` (i.e. 'is even') You would type more characters just requiring the module than you would just using the modulo operator. Then you find out the same author published another module that literally just calls the other one and negates the returned result. Let that sink in: a module, to do nothing more than prefix a function call with a `!`. No fucking surprise the 'ecosystem' is huge. What other people call "writing code" NPM module developers look at as another opportunity to bump their ridiculous package count e-penis. You can use NPM and NodeJS if you want, you can even "like" them. But don't for a second think that the community and practices of that environment are "good" by any comparison. |