re: A JavaScript-Free Frontend VIEW POST

FULL DISCUSSION
 

You are tackling the wrong problems.It's not about refresh button or modularity, its about UI in sync with the State. PWA is not only about loading time, it's also about lesser bandwidth usage. I am assuming you're against local storage and web workers, since it's not HTML or CSS right? I agree with you on 1 thing. Initial loading time of JS frameworks are long, however it can be modified with SSR (server side rendering) and module preloading strategies.

JS frameworks were created to tackle the problems Facebook or Google had with their internal products, its wasn't meant to be used for simple blogs or pizzeria sites.

 

I was fully onboard with all of those benefits of SPAs when I started building them. It never works out in the real world though. "Less bandwidth" is sort of a bogus argument for a couple reasons:

  1. Asana requires 27MB to load first time, 13MB if your cache is primed. Using Slimvoice requires 42KB for your first load and roughly 8KB for every subsequent page load. That means, with some quick math, that you have to perform 1625 page loads/actions in a single session on Slimvoice to make up for the initial load of Asana. I would be surprised if a user did 20 things on Slimvoice over one session. The comparison is slightly apples to oranges but I think I've made my point.
  2. The benefits of all that have turned out to be more theoretical than practical. I'll let JimDabell speak for me here. I too live with a relatively garbage internet connection, and I have not yet encountered a SPA that reliably solves these problems from any size company. It appears that Facebook and Google haven't actually solved it yet.
code of conduct - report abuse