This hits the nail on the head. And is 100% matching our long term thinking. Client-side-only is not sustainable. We need to move more stuff to the server, but without sacrificing seamless composition of interactive pieces.
I know everyone is frustrated with the slow rollout of Suspense for data fetching. But the reason is precisely that we realized it’s unsustainable to put all this stuff on the client as a default solution. It just doesn’t make sense. The server should be a first-class citizen.
Today, client-centered and server-centered are two different ends of the spectrum. You have to design your app in different ways. But what if you didn’t have to choose between the Rails-like model and the client React model? The future is hybrid.
A “disappearing framework” is certainly cool and worth striving for. But it doesn’t help much when the framework is 5% of your code. Say “disappearing app” and I’m listening.
Imagine a CRUD React app with routes — but with no client-side router. Imagine the JS code for most of your components is never shipped to the client — but you can sprinkle some interactivity where you want to. Imagine there was no “backend” because it would be your components.
I don’t know if it makes sense to write about this vision somewhere. Last time we shared our vision, there was a lot of frustration it’s taking much time to ship. So we’re more quiet about it now until we have something you can try.
