Follow

90% of the work in building an SPA is putting back in stuff that the browser would have given you for free if you just hadn't built an SPA

@jalefkowit The whole paradigm is dumb. Now that fiber is everywhere, loading a whole new page is often very very fast.

I made chorebuster.net like it's still 2010 and I'm very happy with the result.

@rimu Only about 42% of the US population has access to at least one fiber broadband provider. Urban areas do a little better than average, but only a little: 46%.

broadbandmap.fcc.gov/#/area-co

@jalefkowit and a lot of problems with SPAs stem from SPA developers implementing *badly* the things that browsers give you for free.

@rysiek Exactly. People really have no idea how much work goes into something as simple as a button.

@jalefkowit The main offender being a download button with progress indicator.

I mean, you totally can use the browser's download indicator in a SPA. If you manage to add the JWT auth info. (Hint: An invisible HTML form button and a simulated click.) But! You're talking to a microservice. Which is asking two other microservices to assemble the data. Progress indicator? Well, add a new API endpoint and poll it, of course! Don't ask me how I know, I would never do this... 😇

Sign in to participate in the conversation
Octodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!