Parse time for javascript on mobile is non-trivial. It has never been more important to ship less code to users. https://youtu.be/jD_-r6y558o pic.twitter.com/CBXH8oc0Ax
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
that's an interesting reading of that result, which is about code that then has to be parsed anyway @samccone @tbreisacher @tdreyno
claiming that JS parse costs are non-trivial is surprising. can u give a better justification? @samccone @tbreisacher @tdreyno
people misunderstood the optimizejs result. lazy parse is bad for code that'll be evalled anyway 1/
but it is very effective on code that *won't be* which is common in real applications 2/
because lazy parse can be effective at unused code 3/
ok, i think we agree on this. but for js on the critical path, @samccone is right, yeah? @tbreisacher @tdreyno
JS off the critical path is super-common, and most likely target for pruning.
sure. @samccone tweets *a lot* about code *on* the critical path. in that case, parse time is real, yeah? @tbreisacher @tdreyno
we tested it, depending from your scenario something is kind of same, some other a lot better!
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.