3 ms·

If so, the failure lies with the spec. (personally, I like ASI)

• umvi 8y ago
  Cue Principle Skinner meme: "Is the language specification too loose?" "No, it's the developers who are wrong."
• nobleach 8y ago
  I feel the same way about ASI as I do about forgiving HTML parsers. They're built to handle mistakes made by your average weekend warrior Grandpa building a website about his grandkids and pets. ASI is built to handle an "oops", not an entire codebase. That's why there are these odd edge cases. The same is true with the English language. If one were to send me a text with "do ya think" I'd probably figure out that it was a question... but why avoid the actual punctuation that assures that I communicate the intention 100%? The explanations that have been given to me typically fall in line with, "well, to new comers, it won't make sense why you don't add a semicolon after a function declaration or if statement. I consider that a teaching moment. But, I'll admit, this debate has little merit. Folks whom are dead set against using them are rarely convinced until they get bitten hard by a 2 hour hunt for an obscure bug. And folks that use them will probably end up with RSI or Emacs Pinky™
  • deleted 8y ago
    [deleted]
  • ng12 8y ago
    > Folks whom are dead set against using them are rarely convinced until they get bitten hard by a 2 hour hunt for an obscure bug. Honestly -- then they'll never be convinced. I haven't hit an ASI bug in the last decade.