7 years ago Apple had to fight rumours about macOS slowly being replaced by iOS due to iOS getting more advanced and a perceived lack of investment in macOS, to the point they had to address this in a keynote. And people *still* didn't believe them. Feels like where React is today with RSC vs SPA.
1. a lot of *other* companies/projects have used "we recommend against X" as a stepping stone to "we are deprecating X"
2. React+co. started recommending against SPA/etc. without going out of its way to explicitly say it'll always work
3. People autocompleted
Ricky and I were discussing similar points the other day in Reactiflux.
Similar to "Redux boilerplate". Adding docs won't fix widespread confusion, but it lets you say exactly the points you want to make clear, and gives a resource to link to every time these conspiracy points come up.
err, self-nit: without going *enough* out of its way. there were a lot of efforts, I think they just weren't able to overcome the never-before-seen (in this specific sub-industry) FUD that came to be
Comments
1. a lot of *other* companies/projects have used "we recommend against X" as a stepping stone to "we are deprecating X"
2. React+co. started recommending against SPA/etc. without going out of its way to explicitly say it'll always work
3. People autocompleted
I tried to add a bit of guidance on architectures in this draft docs PR, but that part didn't get included:
https://github.com/reactjs/react.dev/pull/7618
Feels like it's still needed
Similar to "Redux boilerplate". Adding docs won't fix widespread confusion, but it lets you say exactly the points you want to make clear, and gives a resource to link to every time these conspiracy points come up.
- https://vercel.com/blog/understanding-react-server-components turned into a docs intro page
- modest tech / architecture overview
- FAQ page that answers real and conspiracy points
- adoption guide