Denial of service and source code exposure in React Server Components

Re:Denial of service and source code exposure in React Serve... by stack_framer on Thursday December 11, 2025 @10:32PM (#46240593)

I find myself just wanting to go all the way back to SPAs—no more server-side rendering at all. The arguments about performance, time to first paint, and whatever else we're supposed to care about just don't seem to matter on any projects I've worked on.

Vercel has become a merchant of complexity, as DHH likes to say.

[ Parent | on HN ]

Re:Denial of service and source code exposure in React Serve... by farley13 on Thursday December 11, 2025 @11:05PM (#46240770)

I think the context matters here - for SEO heavy marketing pages I still see google only executing a full browser based crawl for a subset of pages. So SSR matters for the remainder.

[ Parent | on HN ]

Re:Denial of service and source code exposure in React Serve... by robertoandred on Thursday December 11, 2025 @11:56PM (#46241002)

SPAs can still be server rendered.

[ Parent | on HN ]

Re:Denial of service and source code exposure in React Serve... by yawaramin on Friday December 12, 2025 @10:23AM (#46244971)

Htmx does full server rendering and it works beautifully. Everything is RESTful–endpoints are resources, you GET (HTML) and POST (HTTP forms) on well-defined routes, and it works with any backend. Performance, including time to interactive and user device battery life, are great.

[ Parent | on HN ]