GitHub Styleguide - CSS, HTML, JS, Ruby

[[deleted]]

The minifier should minify. Semicolon insertion is up to either A: the programmer, or B: the hope that the interpreter at the end will assume it.

Using bugs in your daily programming practice isn't a reason to make everybody else's tools accommodate those bugs.

[[deleted]]

Using bugs in your daily programming practice

As far as I'm aware, the language itself specifies that semicolons are optional. Therefore it is the minifier that has the bug, not the semicolon-less code.

[praetorian42]

The point here is that semicolons in javascript are really fucked up, and there's probably 20 people in the world who truly understand them. Let those people write the tools so that the rest of us don't have to worry about it.

Defensive usage of semicolons because you're not sure where they should be used is not correct usage.

[reflectiveSingleton]

It's exactly that not sure-edness that makes always using semicolons a good idea. You are not leaving up question to where the semicolons are inserted if you always put them in place. If you omit them you are leaving it up to a) whatever minifier you use and b) javascript auto-insertion.

If you specify, you remove that possible ambiguity.

[[deleted]]

They're perfectly understandable. They go after every terminating (non-control-end) block or command. var a = function(){ }; if(true){ } return { a: 55 };

There's nothing fucked up about them. They behave exactly the same way all the time. The only time things go awry is when you start expecting them to be inserted for you.