3 ms·
Yes, basically. I actually like the premise: > No decisions to make. That can be good, certainly Go developers benefit from the lack of bikeshedding over sty
by Touche 11y ago
Yes, basically. I actually like the premise:
> 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.
- feross 11y ago> If they would have just grepped through NPM to figure out the most popular style choices This amused me, as the npm team themselves use `standard`. https://github.com/npm/npm/blob/master/package.json#L199 https://github.com/npm/npm/blob/master/package.json#L199
- Touche 11y agoGrep through the npm ecosystem, as that serves as a large sample size of what are the standard style choices. I know that npm and it's largely unreadable codebase uses your style.
- artursapek 11y agoThe reason Go is known for this is the gofmt tool. Until there's a good equivalent for JS, thousands of man-hours will continue to be wasted on style-related nonsense like this.