this is nuanced, but the generality of the cost of parse time stands on its own.
-
-
not true in practice. https://github.com/nolanlawson/optimize-js … is one reason.
2 replies 1 retweet 3 likes -
Replying to @wycats
that's an interesting reading of that result, which is about code that then has to be parsed anyway
@samccone@tbreisacher@tdreyno1 reply 0 retweets 1 like -
claiming that JS parse costs are non-trivial is surprising. can u give a better justification?
@samccone@tbreisacher@tdreyno2 replies 0 retweets 0 likes -
people misunderstood the optimizejs result. lazy parse is bad for code that'll be evalled anyway 1/
1 reply 0 retweets 3 likes -
but it is very effective on code that *won't be* which is common in real applications 2/
1 reply 0 retweets 3 likes -
because lazy parse can be effective at unused code 3/
2 replies 0 retweets 2 likes -
eliminating unused code from a payload may have little effect on end-to-end time, and further 4/
1 reply 0 retweets 2 likes -
because people misunderstand lazy parse, it's common to accidentally cause unused code to be 5/
1 reply 0 retweets 1 like -
eagerly parsed (like optimizejs); a combination of changes that drastically reduces code size 6/
1 reply 0 retweets 2 likes
may significantly increase end-to-end time as a result, and I've seen it repeatedly. 7/7
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.