| Vercel is how, and Next.js is like a trojan horse at this point. As much as the React team tries to push back on it, Vercel marketing has become synonymous with React's direction. Most people do not need a single thing that Vercel/Next.js thought leaders are trying to shove down their throats. Unless you're competing with Facebook for SEO rankings (good luck) the 1KB you saved by not shipping an un-interactive component down the wire is nothing. They're actively pushing a set of best practices that align with their hosting model and building a moat around said hosting — Also despite the intentionally confusing wording, Server Side Rendering does work with Client Components! There are literally *hundreds* of posts where people are unaware of that because the directive chosen by the React team was "use client"... which naturally leads people to believe "use client" will opt out of SSR. — To me that choice, and not allowing a project wide disabling of it, were the last straw that took it from innocent misalignment to intentional. By having the thought leaders sell these heavily server involved features they've create a situation where technically you can move your Next.JS project anywhere... there's just a scary (for those who don't know better) laundry list of things that won't work unless a given provider goes out of their way to enable it. They get to play both sides: Next.JS works anywhere (as long as you ignore a bunch if features that we sell as being very important to making a good site) |
I've tried to explain our current terminology here: https://github.com/reactwg/server-components/discussions/4