Live data from Hacker News

If Not SPAs, What?

macwright.com

1–10 of 456 posts

Re: If Not SPAs, What?

#2
If you can do server side great: do it. The difficulty is accurately predicting how much JavaScript you'll end up writing. If your client-side JavaScript is comparable in complexity to your SSR you'll eventually end up with the worst of both worlds.

Re: If Not SPAs, What?

#6
Having mostly used Angular and React with APIs, I recently wrote a small app with server-side templating and a very small amount of jquery. It was an absolute joy. Especially with webpack it feels like the front-end has become needlessly complex and I'm not sure it has improved quality for users.

Re: If Not SPAs, What?

#7
Isn't Next.js (and in turn React, on which Next is built) the answer to that question?

It can do client side rendering, server side rendering, and static site genration.

Re: If Not SPAs, What?

#8
I think Phoenix Live View is maybe the most compelling story around this (https://github.com/phoenixframework/phoenix_live_view). I'm moving a side-project from React/SPA to Phoenix live view and it's kind of amazing to get the dev ergonomics of a server-rendered page with the UX benefits of a SPA.

This course is a pretty great intro: https://pragmaticstudio.com/phoenix-liveview

Re: If Not SPAs, What?

#10
post #8

I think Phoenix Live View is maybe the most compelling story around this ( https://github.com/phoenixframework/phoenix_live_view ). I'm moving a side-project from React/SPA to Phoenix live view and it's kind of amazing to get the dev ergonomics of a server-rendered page with the UX benefits of a SPA. This course is a pretty great intro: https://pragmaticstudio.com/phoenix-liveview

as a user, this is the kind of experience I want on the web. any spa like page should always degrade back to web standards. and it should be lightening fast. and not spin my cpu fan or warm my desk.
Post reply on HN