21–30 of 116 posts
Earlier quoted context omitted.
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).
Of course the solution is to create a separate "standard."
I disagree with some of the rules, but there's clearly merit to having one opinionated, zero-configuration linter-enforced style.
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
I actually got into a Twitter argument with Brendan Eich over it - he more or less won with the note that the tab key in most web editors switches input.
"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 contri…
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
"Standard" for whom? This is just some guy enshrining his preferences.
Calling this "JS standard!" bothers me to no end. I suppose I have to create my own style and call it "standard" too.
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
I hope they enjoy their subtle and extremely hard to find errors.
list.map(func1)
.filter(func2)
.map(func3)
.reduce(func4);
EDIT: Ah, thanks – the things I read never mentioned JS doing lookahead during ASI. This makes it a lot nicer, tbh.