3 ms·
The parent's point can also be interpreted as using simple stuff on client side with the complex stuff on server side. It's what we did for a long time with pre
by nickpsecurity 11y ago
The parent's point can also be interpreted as using simple stuff on client side with the complex stuff on server side. It's what we did for a long time with pretty complex applications. An example of why was a site that uses plenty of JS for almost everything to present entertainment articles. A site like that on dialup pre-Web 2.0 would've loaded all the content in seconds then gradually load the images. On 4G Galaxy 4, the damned thing took 10 seconds to load with parts of the page jumping everywhere. Clicking "next page" literally took 10 seconds each time just so I'd click the right thing.
Whereas, some sites don't have that problem at all since they mostly use HTML and CSS that's cached and fast-loading. Only the JS parts are slow and I usually don't need them. When I do, they've already loaded. I could see alternatives used for something like Facebook but the old stuff would work for over 90% of sites I see. It would also be more efficient outside network transfer. But they usually use CDN's with whole site cached so who cares.