A ton of web frameworks are trying to reinvent WebForms using WebSockets e.g. Phoenix LiveView, the new Blazor components in ASP.NET CORE that uses WebAssembly alongside WebSockets to create a unified stack. Unfortunately the whole web builder concept is no longer popular other than for generic sites, those areas are dominated by companies like Webflow, Weebly, SquareSpace, Pinegrow etc.
What is a "Restful feel"? I didn't think REST was a UI pattern or style.
from https://www.codecademy.com/articles/what-is-rest
>SEPARATION OF CLIENT AND SERVER
>In the REST architectural style, the implementation of the client and the implementation of the server can be done independently without each knowing about the other. This means that the code on the client side can be changed at any time without affecting the operation of the server, and the code on the server side can be changed without affecting the operation of the client.
which is kind of different from having server side "on change" events
Still this describes an "under the hood" implementation technique. It doesn't describe a UI method/technique/style in terms of what the end user sees. The end user's perspective is the key to my question. If that wasn't clear, I apologize.
* One file (script) per route e.g. classic vanilla PHP.
* ASP.NET web forms - tries to make the web like a drag and drop windows forms application. Very nice for basic websites but doesn't scale to well if there are a lot of nested controls. Has this horrible concept called 'viewstate' where you send state about your controls in a hidden form field and post it back. This makes server side "on change" events possible for client side actions. It's horrible because Viewstate size grows quickly for complex forms, and it doesn't feel very web-like or Restful.
If you want to create a SPA, then React/Redux and Elm offer interesting patterns, but your server would still need to send data, and I can't think of anything better than an MC (no V!) type of framework for this.