Not to bring up the idiotic semicolon debate again: but if you write your JavaScript without semicolons, you're forcing everyone else that wants to use your li

Not to bring up the idiotic semicolon debate again: but if you write your JavaScript without semicolons, you're forcing everyone else that wants to use your library to conform to your style guide's rule if they want their code to work: https://gist.github.com/2399955 https://gist.github.com/2399955 The build process will concatenate those two files and your semicolonless JS will cause a bug in my script. That's not being pragmatic, that's just being a jerk to the consumers of your library. I shouldn't have to add unnecessary safeguards to my code because you want to abuse an error-correction feature of the language to avoid typing semicolons. You want to type fewer semicolons, so you force everyone else to add more. /rant