5 ms·
It's a footprint issue, not latency. A 94k jQuery file comes at a price and 99% of that codebase never gets hit for an application like this.
by sintaxi 14y ago
It's a footprint issue, not latency. A 94k jQuery file comes at a price and 99% of that codebase never gets hit for an application like this.
- elliottkember 14y agoThat's not a big footprint for an app, especially compared with image assets, app code and CSS bundled alongside. It also means being able to add more functionality at will without having to rebundle, or worse, work on basic functionality helpers. Just seems like wasted time for such a small improvement. These devices were built to have application code on them.
- eli 14y agoSeems mostly academic, no? Do you think fewer people will download a 1.4MB app versus a 1.2MB app?
- deleted 14y ago[deleted]
- deleted 14y ago[deleted]
- cageface 14y agoZepto is 24k. Does that extra 70k really make that big of a difference? A single retina resolution png is going to be bigger than that. I think there are other reasons to consider a library that's tailored for mobile webkit but size doesn't seem like a dealbreaker.