4 ms·

As mentioned, this article is more about slow internet than about "iffy" internet. People are commenting about the need for slimming down pages, removing bloat

As mentioned, this article is more about slow internet than about "iffy" internet. People are commenting about the need for slimming down pages, removing bloat, but... There are lots of cases for sending MORE data on "iffy" internet connections. One of our websites is a real estate for-sale browsing site (think Zillow). It works great from home or office, but if you are actively out seeing properties it can be real frustrating when Internet comes and goes. Where any interaction with the page can take 10-60 seconds to refresh because of latency and packet loss. A few months ago I vibe-coded a prototype that would locally cache everything, and use cached versions primarily and update the cache in the background. Using developer tools to simulate bad networking it was a day and night experience. Largely because I would fetch first property photos of all properties as well as details about the first few hundred properties that matched your search criteria. "Bloat" when used intelligently, isn't so bad. ;-)

Swizec 1y ago
> A few months ago I vibe-coded a prototype that would locally cache everything, and use cached versions primarily and update the cache in the background. Essentially local-first apps. Have a local database with all the info, use straight up SQL (or whatever) for your interactions, sync periodically with the mothership. Great solution for many usecases. This was one of the original promises of mobile apps and what makes them better than websites. But the industry went a different way – many mobile and desktop apps became glorified browsers where nothing works without good internet.
zdragnar 1y ago
The progressive and offline first features available to browsers now can make for a great experience when you don't absolutely need totally up to date information on the page. So many times I pick up my phone because I'm stuck waiting somewhere, only to realize that I don't have a good connection anymore, and none of the sites I had open are usable anymore.

Swizec 1y ago

> A few months ago I vibe-coded a prototype that would locally cache everything, and use cached versions primarily and update the cache in the background. Essentially local-first apps. Have a local database with all the info, use straight up SQL (or whatever) for your interactions, sync periodically with the mothership. Great solution for many usecases. This was one of the original promises of mobile apps and what makes them better than websites. But the industry went a different way – many mobile and desktop apps became glorified browsers where nothing works without good internet.

zdragnar 1y ago

The progressive and offline first features available to browsers now can make for a great experience when you don't absolutely need totally up to date information on the page. So many times I pick up my phone because I'm stuck waiting somewhere, only to realize that I don't have a good connection anymore, and none of the sites I had open are usable anymore.