If the js community spent half as much writing valid concatenators and compressors as hacks to avoid crap, then ;!(...)();\n would die
-
-
@bascule i've never seen a return violation in the wild. i'm sure it could happen, but seriously? do you even unit test?Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
-
@oscardelben@bascule then stop using shit concatenators. there are plenty of real JS parsers out there, just no one uses them to PARSE JS. -
-
@oscardelben@bascule yes, we used a non-parsing/rewriting concatenator. I remember. afaik, closure is the only parser in regular use.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.