> One company I advise tried it, and found that its "unsyntax" bit back in > this way: code that compiled and seemed to do one thing did something quite > different. This happens with JS due to ASI; it also happens just due to the > C syntax heritage. But it happens more often with CoffeeScript, from what I > hear. > > More of an issue with CoffeeScript's grammar, which is ambiguous in lots of places, and with what I believe to be some bugs in the parser (those Michael Ficarra could probably fix in CoffeeScript redux). I had some examples back in the days I tried CoffeeScript where one-character differences in an object declaration could lead to four entirely different object definitions.
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
