Most are older and don't want to spend the obscene prices for satellite, cellular signal isn't good enough out there.
(I haven't personally had dial up in about 20 tears.)
Sites that work well with lynx are OK on dial up.
A couple examples:
I literally cannot imagine 56K on the modern web.
Comcast and/or Century Link would be willing to set the neighborhood up, for a pretty sizable fee.
(Sorry to slightly hijack the thread. It's been an ongoing debate on HN)
Traditional server-rendered HTML should be orders of magnitude faster than most SPA bundles though.
I'm talking about long-lived apps where work is being accomplished. An SPA allows downloading and caching al or most of the frontend, then further communication can proceed using minimal bandwidth as the user works.
With traditional SSR, every page/form the user navigates to requires downloading all markup, styles, and client-side behaviors for that route.
I'm willing to believe SPAs with everything handwritten, containing just the necessary code, could work but that's not how SPAs are usually written.
Not only this but very simple HTML with POST forms, in addition to being lightweight, benefit from a very robust handling, where you can retry stuff and all. SPA are usually bad at this.
All markup needs to be downloaded but it might be very light, and styles are hopefully cached, so it's an issue on first load only and SPAs don't solve this.
Or a terminal UI, since that usually worked well back when dial-up was common.
I haven't found this to be the case at all. What apps are you using?
>Maybe in a PWA where the service worker gets saved for offline use.
You know browsers have caches, right?
Although native downloaded apps will probably be more usable & familiar in that case.