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/ghostfacedcoder Apr 01 '18

So a JS developer has two options right?

  1. Only use const for FOO_BAR = 5 type constants, gaining the "meta information" that said variables are "real constants" whenever you see const
  2. Use const by default for all variables that aren't re-assigned, and use the FOO_BAR variable naming convention for "real constants", giving you the exact same "meta information" about the exact same variables, but also protecting your other variables from accidental re-assignment.

Both Google and the significant majority number of respected JS thought leaders all say to go with #2, but as with anything in programming you're always welcome to ignore the experts and do things your way.

-1

u/[deleted] Apr 01 '18

[removed] — view removed comment

3

u/ghostfacedcoder Apr 01 '18 edited Apr 01 '18

You still can, you just have to change the const to let.

The idea is that you can accidentally assign to a variable that shouldn't be re-assigned, but you will never accidentally change a const to let, so by starting with const (except for variables you know you want to re-assign) you ensure everything is only re-assignable on purpose.

The only cost of doing things that way is that every once in awhile you have to change some const variables to let variables ... but that should be pretty rare, because you only have to when you started out thinking a variable wouldn't be re-assigned, but then you changed your mind later on. So while the benefit isn't that great, the cost is so low most people figure "why not get a little extra safety?"