so, here's the deal. i do perf as part of my day-to-day job. so, when i hear @samccone say "parse time matters" i nod my head 1/
-
-
because i've seen that shit, yo. i've seen parse times of compiled handlebars templates lock up mobile devices. 2/
@samccone2 replies 0 retweets 0 likes -
i've seen "lightweight"backbone code chug on an ajax response for 2 seconds. 3/
@samccone1 reply 0 retweets 0 likes -
i guess what i'm saying is, parse time *does* matter for perf-sensitive code. claiming otherwise is silly and wrong. 4/4
@samccone3 replies 0 retweets 2 likes -
I don't disagree AT ALL with the empirical facts. I do, however, think that people are making counterproductive decisions
1 reply 0 retweets 3 likes -
on the basis of oversimplistic reasoning that looks waaaay too close to these true facts.
1 reply 0 retweets 3 likes -
and by counterproductive I mean months of work to cut down size leading to *increases* in end-to-end time.
1 reply 0 retweets 2 likes -
yeah this is why MEASURE MEASURE MEASURE before doing anything ;)
2 replies 2 retweets 9 likes -
a model of the dependencies for a page load where we can cheaply try different optimizations w/o actually implementing.
@wycats2 replies 0 retweets 1 like
we've been talking about this in @emberjs - I have some ideas on how to speed up the feedback loop.
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.