[pmontra]

> The major SPA frameworks are all moving to an RPC model of all things, entirely coupling your frontend and back end together.

I'm not familiar with this development. Do you mean that for example React has grown a backend running on a server, querying the database, etc?

I know that backend frameworks like Rails and basically all the major ones added a JS layer running inside the browser and obeying to the backend. It listens to messages from the backend with changes to the UI elements and that saves full page reloads.

[_heimdall]

I'm thinking mainly about about SPA frameworks (metaframeworks?) like NextJS, SvelteKit, Remix, and I think NuxtJS as well though I'm less familiar.

They're all adding features where code is marshalled back to the server either through useServer() hooks, pragmas, or magic $ signs and imports.

They all create RPC calls as part of the build and bundle step. Depending on the specific implementation, that usually means taking code that otherwise looks like client code, moving it to the server bundle with a unique API signature, and swapping the RPC API call into the client code.

[mattmcknight]

> backend frameworks like Rails

Rails has been a full stack framework since the start, with the JS component changing frequently over the decades, but with template helpers that generate JS being a fundamental component since the beginning.