3 ms·

Ensuring your app loads quickly over the network is definitely an optimization, but to call it a micro-optimization is wrong. Size on the wire for html5 apps (f

by potch 13y ago

Ensuring your app loads quickly over the network is definitely an optimization, but to call it a micro-optimization is wrong. Size on the wire for html5 apps (frequently loaded over mobile connections) is completely relevant.

dvt 13y ago
3g is virtually ubiquitous. And building an app having weird contingencies in mind (atrocious wifi connections, 5 billion people downloading simultaneously, downloading from outer space, etc.) is not good engineering. Unless you like spending time in development hell. "Oh no, our application can't be simultaneously downloaded by 3 million martians because our client is too big." I'm being facetious, of course, but I think the point applies. Don't build stuff with weird contingencies in mind. The average user (of an HTML5 app) will not have to worry about processing power, bandwidth, or client size. As long as it's not like 20mb or something stupid.
- discreteevent 13y ago
  I'm reading your comment on an intermittent 2.5 g connection.
- ricardobeat 13y ago
  It is well known that lower response times increase conversions and reduce abandonment on any website. There is absolutely no reason for a website to cross the 1-2mb threshold unless it's a huge web application, a game or image-based app, or is serving you hi-res photos. And, obviously, websites are accessed from all kinds of connections. Not everyone has a generous 3G plan, and even the US doesn't rank that well in average broadband speeds.
- mikeash 13y ago
  3G isn't nearly fast enough to make megabytes irrelevant.
- Millennium 13y ago
  One third of the US audience is not a "weird contingency"; it's basic awareness. Developing only for the highest of the high end is not good engineering. Get your head out of the cloud.
wnsnw 13y ago
Those in that situation should probably start by optimizing the whole "frequently loaded" part... by not frequently loading it. Then they would realize this shaving of a few hundred bytes here and there is, indeed, micro-optimization.

by potch 13y ago

dvt 13y ago

3g is virtually ubiquitous. And building an app having weird contingencies in mind (atrocious wifi connections, 5 billion people downloading simultaneously, downloading from outer space, etc.) is not good engineering. Unless you like spending time in development hell. "Oh no, our application can't be simultaneously downloaded by 3 million martians because our client is too big." I'm being facetious, of course, but I think the point applies. Don't build stuff with weird contingencies in mind. The average user (of an HTML5 app) will not have to worry about processing power, bandwidth, or client size. As long as it's not like 20mb or something stupid.

discreteevent 13y ago
I'm reading your comment on an intermittent 2.5 g connection.
ricardobeat 13y ago
It is well known that lower response times increase conversions and reduce abandonment on any website. There is absolutely no reason for a website to cross the 1-2mb threshold unless it's a huge web application, a game or image-based app, or is serving you hi-res photos. And, obviously, websites are accessed from all kinds of connections. Not everyone has a generous 3G plan, and even the US doesn't rank that well in average broadband speeds.
mikeash 13y ago
3G isn't nearly fast enough to make megabytes irrelevant.
Millennium 13y ago
One third of the US audience is not a "weird contingency"; it's basic awareness. Developing only for the highest of the high end is not good engineering. Get your head out of the cloud.

wnsnw 13y ago

Those in that situation should probably start by optimizing the whole "frequently loaded" part... by not frequently loading it. Then they would realize this shaving of a few hundred bytes here and there is, indeed, micro-optimization.