"Standard" for whom? This is just some guy enshrining his preferences.
> No decisions to make.
That can be good, certainly Go developers benefit from the lack of bikeshedding over style.
But the authors of standard didn't take this advise; they did make decisions, the ones that they prefer. If they would have just grepped through NPM to figure out the most popular style choices I would have respected the idea a bit more.
This amused me, as the npm team themselves use `standard`.
Calling this "JS standard!" bothers me to no end. I suppose I have to create my own style and call it "standard" too.
signed, The entire Python community (well, most of us...)
But this isn't a real web standard!
Of course it's not! The style laid out here is not affiliated with any official web standards groups, which is why this repo is called feross/standard and not ECMA/standard.
The word "standard" has more meanings than just "web standard" :-) For example:
This module helps hold our code to a high standard of quality.
This module ensures that new contributors follow some basic style standards.