News for hackers. Stuff that matters.
Re:5 Things They Told You Not To Use In JavaScript by ahoyhere on Tuesday April 24, 2012 @07:32PM (#3886884)
> These are weasel words.

No, actually, that's how it works in JS. ASI doesn't "work" in all cases because a line break doesn't always indicate the end of a statement. No less than Brendan Eich wrote this himself, in his blog post reply to the whole "semicolongate" which happened a couple weeks ago.

I'm sure it feels good to be all righteously angry… but it helps to be right.

Re:5 Things They Told You Not To Use In JavaScript by slexaxton on Tuesday April 24, 2012 @07:39PM (#3886919)
Brendan's other words included:

> My two cents: be careful not to use ASI as if it gave JS significant newlines.

http://brendaneich.com/2012/04/the-infernal-semicolon/

Re:5 Things They Told You Not To Use In JavaScript by ahoyhere on Tuesday April 24, 2012 @08:22PM (#3887055)
Yes, and that's an opinion. And he doesn't say it is a fact.
Re:5 Things They Told You Not To Use In JavaScript by MatthewPhillips on Tuesday April 24, 2012 @07:40PM (#3886922)
http://www.thefreedictionary.com/weasel+word

> Weasel word: An equivocal word used to deprive a statement of its force or to evade a direct commitment.

From the article, emphasis mine:

> A linebreak indicates, in most cases, the end of a statement;

Re:5 Things They Told You Not To Use In JavaScript by ahoyhere on Tuesday April 24, 2012 @08:15PM (#3887030)
That's like saying that "Car crashes, in most cases, are not fatal" is weasel words at work, when in fact it's simply a fact. Car crashes are not fatal, in most cases. And in JS, a line break indicates the end of a statement, in most cases. It's in the spec for ASI.