3 ms·
I don't develop phonegap apps but I'll have a go at answering this: > I'm still confused why this matters if you are packaging your assets with the phonegap bu
by grayrest 14y ago
I don't develop phonegap apps but I'll have a go at answering this:
> I'm still confused why this matters if you are packaging your assets with the phonegap build which I would expect most people do.
Ignoring download time, loading, parsing, and evaluating 250k of javascript is not free[1].
[1] http://carlos.bueno.org/2010/02/measuring-javascript-parse-and-load.html http://carlos.bueno.org/2010/02/measuring-javascript-parse-a...
That article is on a desktop (well, laptop) processor. The timings on mobile are obviously higher. JS parse & load is mostly ignored on the desktop but I know I've read at least one article where a team was pulling down their JS as plain text and eval()ing it later to get their load times down.
- johnbender 14y agoI'd be interested to see the actual numbers for jqm here but I don't think the 100-150ms initial load time is a deal breaker for almost any app. Your point is well taken though, and thanks for the link.
- joemoon 14y agoIt's more like 800-900ms. Here is a link to the jquery init time on Android: https://docs.google.com/spreadsheet/ccc?key=0Aq_a4WNAMuCEdDdjSlhyWXJaTkQ0TVJFc1k1RzlTTlE#gid=0 https://docs.google.com/spreadsheet/ccc?key=0Aq_a4WNAMuCEdDd... I don't recall when this kind soul made this document public, but I believe it was in a similar discussion on hacker news and I've had it bookmarked since. I have also done my own tests, and the iOS numbers are similar (depending on the device of course).