31–40 of 116 posts
Earlier quoted context omitted.
Let's just say that coupling this preference with the name "standard" is an extremely contentious decision (search the github issues).
https://github.com/Flet/semistandard Of course the solution is to create a separate "standard."
I've been lucky enough to avoid having to deal with a style guide in a long time. The general idea is sound, but such a guide is always accompanied by hours-long meetings of senior developers hurling their egos at each other over an issue like semicolon usage. Such a waste of everyone's time.
"Standard" for whom? This is just some guy enshrining his preferences.
Earlier quoted context omitted.
Let's just say that coupling this preference with the name "standard" is an extremely contentious decision (search the github issues).
https://github.com/Flet/semistandard Of course the solution is to create a separate "standard."
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.
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
Maybe if I was using Python or Ruby. But JS? REALLY ugly practice. Multiple blank lines not allowed? I usually go with two to segment heavily procedural code. The most appalling thing by far though is spaces instead of tabs... what's wrong with this guy?
It's misplaced passion and I don't care.
"Standard" for whom? This is just some guy enshrining his preferences.
This. Calling this "JS standard!" bothers me to no end. I suppose I have to create my own style and call it "standard" too.
This 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.
"Standard" for whom? This is just some guy enshrining his preferences.
This. 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
That's how I felt about spaces instead of tabs. 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.