I've run across far too many "mobile-friendly" websites that start by loading many MBs of JS libraries. And just flat-out fail to load if any of said libraries fail to load.
I'm talking about bad connections, not necessarily mobile. This applies especially to situations that companies like G-Advetures face. In South America they have to deal with perfectly fine desktops, but very high latency internet connections. Submitting a form can take 20 minutes or more.
A text only version like the one described would be far worse than a JS heavy one. JS free forms are naturally synchronous. So each edit would kill the ui for a full refresh cycle.
On the other hand a SPA type page can send data in the background white you're doing other work in the app.
Sure there are crappy mobile friendly sites, but that doesn't invalidate the idea.
On a side note I'm not really sold on the whole CDN idea, it just looks like another HTTP request and another point of failure. Concatenate / uglify seems like the better solution.
The idea would be that for a web app, posting or fetching little bits of JSON every time an action is taken would be less intense than getting a whole page every time. Of course, as you have experienced, that's not helpful if the initial page load is too heavy. Also it's not too helpful for sites that have content to read, rather than actions to take.
ps. "citation needed" is kind of obnoxious when it's something you can think through for yourself.
Comments
[Citation needed]
I've run across far too many "mobile-friendly" websites that start by loading many MBs of JS libraries. And just flat-out fail to load if any of said libraries fail to load.
I'm talking about bad connections, not necessarily mobile. This applies especially to situations that companies like G-Advetures face. In South America they have to deal with perfectly fine desktops, but very high latency internet connections. Submitting a form can take 20 minutes or more.
A text only version like the one described would be far worse than a JS heavy one. JS free forms are naturally synchronous. So each edit would kill the ui for a full refresh cycle.
On the other hand a SPA type page can send data in the background white you're doing other work in the app.
Sure there are crappy mobile friendly sites, but that doesn't invalidate the idea.
On a side note I'm not really sold on the whole CDN idea, it just looks like another HTTP request and another point of failure. Concatenate / uglify seems like the better solution.
The idea would be that for a web app, posting or fetching little bits of JSON every time an action is taken would be less intense than getting a whole page every time. Of course, as you have experienced, that's not helpful if the initial page load is too heavy. Also it's not too helpful for sites that have content to read, rather than actions to take.
ps. "citation needed" is kind of obnoxious when it's something you can think through for yourself.