> Critical Security Vulnerability in React Server Components

RSC isn’t React.

> Next.js 15.1+ is unusable outside of Vercel

Next.js isn’t React.

By contrast to nextjs, React + Vite is quite a nice combo. Maybe Bun or Deno are also good? But nextjs and RSC should be kept separate from the discussion.

With React I find there is usually a clear and simple way to achieve what you want, and while it doesn’t perform super well, my customers get more value from a maintainable codebase than a fast one - because I can add features faster.

▲

rk06 4 hours ago | parent | next [-]

why is RSC not considered react? it is designed by core React team, and heavily recommended by core React team. and needs deep support from react.

▲

jamesrr39 3 hours ago | parent | next [-]

Subjective depending on who you ask, but for me RSC is not really representative of React usage. (I believe) the vast majority of React apps (and the vast majority of dev experience in React) are front end only. I have been writing React in some form for 8+ years, but never touched RSC.

	▲	pjmlp 3 hours ago \| parent [-]
		It is, especially in big corps doing MACH with SaaS products, deploying into Vercel.

▲

cadamsdotcom 4 hours ago | parent | prev [-]

Doesn’t mean you have to use it.

▲

nicce 3 hours ago | parent | prev | next [-]

> Next.js isn’t React.

But it seems becoming. Many React maintainers are on Vercel's payroll and Next.js is also defining where React is going.

▲

z3ratul163071 4 hours ago | parent | prev [-]

this a million times. the next.js intermixing of backend / frontend code is a security nightmare.