I sometimes wonder why all JS minifiers prefer to emit semicolons when they could leverage ASI and emit newlines instead. ASI is terrible for authoring (don't @ me!), but in this case it would produce exactly same byte size yet much more readable output.
-
-
I'm pretty sceptical that it would be a real problem, but wouldn't mind to be proven wrong.
-
Even if the transport format is tight because of compression, it still takes up memory in Chrome! Oh no, all those bytes! Also it's actually somewhat easy to get ASI wrong :) Happens to me all the time... !function (a) { console.log("Hello "+ a); } ("world"); oops.
- 11 more replies
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.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.