Hacker News Reader

but if we're talking about building an SPA you're typically going to be building a worse solution if you can't SSR your client views

Is not worse, is fine. Mostly depends on the requirements, why go the extra complexity of SSR if you don't need it?

View on HN

Most of the time SSR gives massive web accessibility benefits. Ignoring web accessibility because you don't want to implement SSR is likely a worse solution for a large portion of your userbase.

That's why I said "typically". One of the biggest complaints about SPAs is the perceived slowness due to the app loading and rendering assets in the browser, as well as the typical HN noscript complaints, as well as accessibility issues, SEO issues, and other problems related to back button behavior and url routing. SSR solves all of these troubles.

Reply on news.ycombinator.com