But why would Elm be any different? (I understand that it is, but there's no rational reason I can see that this has happened to JS and not other languages, esp things that compile to JS where the anemic std lib argument doesn't even really apply)
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
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
`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
-
-
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.
-
There are also 162 packages which do the same thing but in browser environments. They are incompatible with the packages which support node.
End of conversation
New conversation -
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.