top | item 18317909

(no title)

I can't say I fully comprehend the SSR vs SPA war. Both concepts are definitely being misused/overused, one is "dated" and the other "modern", but surely the middle ground where best usage of both can be attained is prefered. I don't know of any terms that mediate the opposition other than perhaps "hydration"?

discuss

sam0x17|7 years ago

This is the key. There are super developed SSR frameworks and super developed SPA frameworks, but getting the two to work together is like pulling teeth. No one tries to write an SSRSPA framework because that would be considered too "opinionated", but maybe that's exactly what we need.

kraftman|7 years ago

Doesn't nextjs do this already? You write an SPA that nextjs implicitly also knows how to render server side

btmorex|7 years ago

If you're using node.js and redux, then https://github.com/faceyspacey/redux-first-router pretty easily gets you there. Other than turning route changes into redux actions, I don't find it particularly opinionated.

jotto|7 years ago

I made https://www.roast.io/ because of this.

Most of the current SPA frameworks can re-hydrate SSR'd JS without issue, so instead of configuring SSR, just use a headless browser, which is what Roast does.

friedman23|7 years ago

Ok, I was confused by your comment and the other person's comment. SSR and SPA are not mutually exclusive things.