I started skimming the rules and was like "this all seems fine" and then noticed "no semicolons". YOU'LL PRY THEM FROM MY COLD, DEAD HANDS FIRST
That is a really bizarre choice since I think "no semicolons" is the less popular position by far.
Proposed JavaScript Standard Style
11–20 of 116 posts
Re: Proposed JavaScript Standard Style
#12I switched to this style a few months ago, and really like it. Makes javascript read more like python, clean and specific.
Downside is that very few other authors are using it, so when you share code people are concerned about its format (no semicolons in particular).
Re: Proposed JavaScript Standard Style
#13Reminds me of that: https://xkcd.com/927/
Re: Proposed JavaScript Standard Style
#14I started skimming the rules and was like "this all seems fine" and then noticed "no semicolons". YOU'LL PRY THEM FROM MY COLD, DEAD HANDS FIRST
That is a really bizarre choice since I think "no semicolons" is the less popular position by far.
Let's just say that coupling this preference with the name "standard" is an extremely contentious decision (search the github issues).
Re: Proposed JavaScript Standard Style
#15I started skimming the rules and was like "this all seems fine" and then noticed "no semicolons". YOU'LL PRY THEM FROM MY COLD, DEAD HANDS FIRST
no semicolons = no deal
Re: Proposed JavaScript Standard Style
#16This is not a solution to any problem, except the problem of not enough standards
Re: Proposed JavaScript Standard Style
#17"Standard" for whom? This is just some guy enshrining his preferences.
This is addressed in the README
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.Re: Proposed JavaScript Standard Style
#18"Standard" for whom? This is just some guy enshrining his preferences.
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.
Re: Proposed JavaScript Standard Style
#19I started skimming the rules and was like "this all seems fine" and then noticed "no semicolons". YOU'LL PRY THEM FROM MY COLD, DEAD HANDS FIRST
I hope they enjoy their subtle and extremely hard to find errors.
I alternate between projects with and without semicolons, and I'm yet to run into a single error as a result of omitting a semicolon. I don't understand what kind of code other people are writing that does.
Re: Proposed JavaScript Standard Style
#20This seems like a great style, but it's not going to catch on because it's a separate dependency. If this were distributed as a configuration file for the most commonly used linters, I'd be interested. Since it's its own linter with its own plugins etc, hard pass.