moot✳
A little more connected.
Join Moot
15 comments

Totally agree.

The product we're working on now uses plain React, Vite, and basically no frameworks/libraries at all.

AI can perfectly write its own state management and query caching, etc, with Reacts bare essentials, no need for all that fancy bloat anymore.

I’m still using TanStack Router (because React routing is still not solved somehow in 2026).

For a logged-in dashboard, client rendering can be a lot simpler. Public discovery pages might still benefit from prerendering, without paying the SSR cost on every app screen

Honestly, a simple SSG like Astro or 11ty is all I need for public marketing pages. I’d never use React to build a public site.

behind a login, i'd start with a static shell and load the data in the browser. paying for a server render there is a hard sell.

Not sure if RSC and SSR were genuinely needed or if hosting companies promoted it for profit.

If SSR is expensive for your app you should try https://proa.so/. Fastest component based SSR on the market. Would love your thoughts on it.

proa.so

I don't want SSR.

My take is that if you don't SSR, you pay for it with large JS bundles that ship to the client and longer client side execution with CSR. The problem was never SSR itself, it's that it's expensive with JS, which is what I'm trying to solve with Proa

He doesn’t want SSR.

Let me put it more clearly: SSR is a dumb fucking idea that solves no problem unless you care about SEO and have incredibly niche problems.

Agree. What do you suggest instead?

Just regular client-side React. I'm using TanStack Router + Hono for some of my projects.