← Back to context

Comment by nosioptar

5 days ago

DSL isn't available at all to them. The phone infrastructure in their neighborhood is ancient, there's zero cable.

Comcast and/or Century Link would be willing to set the neighborhood up, for a pretty sizable fee.

9 comments

nosioptar

Reply
TimTheTinker  5 days ago

Here is an excellent use case for SPA web apps. See - a lot of low bandwidth connections still exist in the US.

(Sorry to slightly hijack the thread. It's been an ongoing debate on HN)

  • jtbaker  5 days ago

    How does this make sense? SPAs have notoriously large bundles shipped to the client. Maybe in a PWA where the service worker gets saved for offline use.

    Traditional server-rendered HTML should be orders of magnitude faster than most SPA bundles though.

    • wtallis  5 days ago

      With a dial-up connection, you really want a native app that only hits the network for functionality that fundamentally needs to be done over the network. And you want the app to be hitting stable APIs, rather than requiring weekly updates to keep it in lockstep with a front-end server's constant development churn.

      Or a terminal UI, since that usually worked well back when dial-up was common.

    • TimTheTinker  5 days ago

      For content-driven sites - absolutely.

      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.

      1 reply →

    • ycombinatrix  3 days ago

      >SPAs have notoriously large bundles shipped to the client.

      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?