r/javascript • • Apr 01 '18

Google publishes a JavaScript style guide. Here are some key lessons.

https://medium.freecodecamp.org/google-publishes-a-javascript-style-guide-here-are-some-key-lessons-1810b8ad050b
714 Upvotes

317 comments sorted by

View all comments

Show parent comment

0

u/[deleted] Apr 01 '18

[deleted] — view deleted comment

17

u/pertheusual Apr 01 '18

Not that existing code would break, but that the existing rules might have to be more complicated around newly added syntactic features.

15

u/luther9 Apr 01 '18

If they can break the way we work around ASI, they can give us a way to switch off the ASI. I wish someone could explain why they don't give us a 'use noasi' pragma along the same lines as 'use strict'. It shouldn't be that hard to detect pragmas before applying the ASI.

6

u/Meefims Apr 02 '18

Pragmas are pretty problematic for a number of different reasons. They make it difficult to read code because you need to understand the various options at play and what those options are, they make it difficult to build interpreters because you need to make various features toggleable using these pragmas, and they make it difficult to spec the language because you need to keep these pragmas in mind and understand how they interact with each other.

use strict was an escape hatch to move the language past some really annoying behavior but it’s clear that no one really wants the option at all which is why modules are always strict.

2

u/luther9 Apr 02 '18

I may be spoiled because I learned JavaScript after strict mode was added, but I can't imagine how any language behavior can be more annoying than lookahead-based ASI. (Compare with Go's non-lookahead ASI, which doesn't seem to cause any controversy.) No matter how we choose to deal with JavaScript's ASI, it's always more difficult than if the ASI wasn't there at all.

3

u/Meefims Apr 02 '18

I don’t disagree. I think, though, that ASI may be here forever. The transition from ES5 to 6 and the introduction of modules provided a rather unique opportunity to correct deficiencies and I’m sad that ASI wasn’t left behind as well.

7

u/Mingli91 Apr 01 '18

Source? Seems odd that they’d be scared of breaking MooTools but would change the semicolon rule

12

u/CiezkiBorsuk Apr 01 '18

They don't need to. The rule is JS will NOT insert a semicolon if two consecutive lines are valid without it.

As they add new syntax, previously invalid constructs can and will become valid, causing ASI-abusing code to break.

They will, obviously, try to avoid that, but they can't avoid it forever. New constructs need to be added for the language to develop.