That issue would have been fixed by making semis mandatory in classes, which is perhaps what we should have done.
I don't understand. Programmers are the target audience for all of JS no?
-
-
Yes, so can we rely on that person to see an issue and correct it(ASI issues with class props). Again they're not using a linter, prettier or writing tests. Assumingely if they're "professional" programmers, they're getting paid to solve problems already.
-
From this perspective, why do you care what TC39 recommends?
-
I care very much.We choose no-semi at work because that's what we like as a team, plus we do ruby. When we bring on new devs and they are reading that TC39 recommends using semi colons, we have to explain now why we are going against TC39 instead of just personal taste
-
I think it would make sense for us to update the guidance to specifically say that using an up to date linter tool is acceptable too. fwiw my company does Rails for the backend (big app) and JS for the front and using semis for JS isn't bad. But I respect the style.
-
Awesome! And yes as a Rails and Ember user I know who you are. Haha
. I do respect both styles, but seeing this thread, maybe no-semi devs are under represented on TC39? Not sure. -
They definitely are.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
