SPA Usage Debate
Discussions debate the necessity, benefits, and drawbacks of Single Page Applications (SPAs) compared to traditional server-side rendering and multi-page websites, questioning when SPAs are appropriate.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Why would you build a SPA, if not for a more snappy user experience?
SPA make sense whenever you want to write a proper application running in the browser. When you just want a website, stop the SPA madness.
See, you don't always need a SPA, you know.
Nobody needs an SPA, it’s a stylistic choice, not a need.
The world vastly over estimate what needs to be a SPA.
All of your benefits seem to come from using only rest APIs to drive to site. That alone can be done with any site, but SPA usually implies more.
Seriously, you don't really seem to know what you're talking about.You can do it either way, and your particular example is a really poor reason to have a SPA.As multiple people are trying to tell you.
It's because SPAs are a fad and server-side rendering is both faster and better for the client.
Serious question:Is this really a problem with web developers? Or is it with product managers who demand SPA like behavior?
i don't get it. isn't this just traditional SPAs but worse and more limited in basically every way?