[Gigachad]

I think the server side rendering part of rails has largely become obsolete but the api backend side of rails is still going strong. Some day other things like rust might replace it but I don’t see that happening any time soon.

[digisign]

Hmm, SSR is used quite often, it has just reached the boring stage. Also, rust is too BDSM for rapid CRUD building needs.

[Gigachad]

Obsolete is probably an overstatement but its in decline IMO. The last few companies I have worked at have moved away from SSR which seems to reflect a wider industry trend. I have worked mostly in enterprise web apps which client side rendering suits better which might have some bias.

[ryanbrunner]

If anything, I've seen the start of the reverse happening. The warts are starting to show on the pure SPA approach, and people are either finding ways to do more SSR with the SPA tools, or taking new approaches like LiveView in Phoenix or Hotwire in Rails to provide richer experiences while still generating HTML on the server.

The heyday of "SPA is the right approach for everything" feels like it peaked at least a few years ago.

[cutler]

Your sample is hardly representative. The big-league Node frameworks are all SSR-based due to the problem presented by pure front-end SPAs. Have a look at Next.js and Remix.