That's what's so interesting/frustrating here. Why did it happen to JS but nowhere else? JS didn't always have this culture. What changed? Why hasn't every popular language since NPM took off had the same effect?
-
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
Replying to @JAH2488
I mean I could see that argument, but that's not where we are now. In the time when I was writing a lot more JS most of what you saw were things like moment.js and underscore, which are reasonable sizes for that sort of library
2 replies 0 retweets 0 likes -
This Tweet is unavailable.
-
Replying to @JAH2488
I agree, but it'd have to by necessity. Underscore is at least 200-300 libraries in the NPM world, not including transitive dependencies. :)
1 reply 0 retweets 1 like -
I still don't necessarily think that the SRP argument leads to this level of extremism though. And TBH anyone using "the unix mindset" as an argument for microlibraries should look at the line count (or just the manpage) of all the unix utilities they use to elevate this argument
2 replies 0 retweets 1 like -
`sort` as an NPM package. There are at least 50 packages covering the various available options. On top of that there are another 25 that are non-configurable, claiming to be the "default sort". 68 of these are unmaintained but don't indicate as such. 72 are 0.x
1 reply 0 retweets 1 like -
Let's add another 25 packages that are just plain broken to bring us to a nice round 100. There are 8 standardized environment variables taken into account by `sort`. Of the NPM packages, 30 of them respect at least one of them. No packages respect all of them.
1 reply 0 retweets 1 like
There are also 162 packages which do the same thing but in browser environments. They are incompatible with the packages which support node.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.