←back to thread

Denial of service and source code exposure in React Server Components

(react.dev)
298 points sangeeth96 | 1 comments | 11 Dec 25 20:46 UTC | HN request time: 0s | source
Show context
chuckadams ◴[11 Dec 25 21:06 UTC] No.46237166[source]▶
I remember when the point of an SPA was to not have all these elaborate conversations with the server. Just "here's the whole app, now only ask me for raw data."
replies(7): >>46237234 #>>46237514 #>>46237562 #>>46237703 #>>46237856 #>>46238657 #>>46239228 #
pjmlp ◴[11 Dec 25 21:51 UTC] No.46237703[source]▶
Until they discovered why so many of us have kept with server side rendering, and only as much JS as needed.

Then they rediscovered PHP, Rails, Java EE/Spring, ASP.NET, and reboted SPAs into fullstack frameworks.

replies(2): >>46238277 #>>46238386 #
sangeeth96 ◴[11 Dec 25 22:37 UTC] No.46238277[source]▶
> Then they rediscovered PHP, Rails, Java EE/Spring, ASP.NET, and reboted SPAs into fullstack frameworks.

I can understand the dislike for Next but this is such a poor comparison. If any of those frameworks at any point did half the things React + Next-like frameworks accomplished and the apps/experiences we got since then, we wouldn't be having this discussion.

replies(7): >>46238440 #>>46238587 #>>46238618 #>>46238988 #>>46239039 #>>46240341 #>>46241462 #
1. tacker2000 ◴[11 Dec 25 23:46 UTC] No.46238988[source]▶
How does Next accomplish more than a PHP/Ruby/whatever backend with a React frontend?

If anything the latter is much easier to maintain and to develop for.