There will be no need for JS on most sites, can be adapted to current frameworks, and with preload/prefetch it might be very fast.
* U can prefetch progress bar / loading state for example, and redirect to partial url of a real content
intercooler also supports something similar to the server pushed DOM diff flow you envision:
Server Sent Events BETA (http://intercoolerjs.org/docs.html#sse)
"Server Sent Events are an HTML5 technology allowing for a server to push content to an HTML client. They are simpler than WebSockets but are unidirectional, allowing a server to send push content to a browser only." http://intercoolerjs.org/docs.html#sse
I, like many other, spending some time to ensure server side rendering works, and web site can function without JS. If intercooler were part of browser, and not separate code it will be possible to adapt any SSR ready app to work with this.
I am not sure if interaction is possible as part of the mix using some tricks, though. It seems like we just have turbolinks for that.
Edit: It works only with svg and only in Firefox, or am I doing something wrong?
- Client sends the entirety of what it has to the server so the server can do the diff
- Server sends the entirety of the new page to the client so it can do the diff
- Server is constantly keeping track of the last thing that the user looked at so it can send the diff for the next page
?Server can generate UI with baked changes to state. URL parameters. Generate html from received state by calling render function of clicked component and send just that components html.
If we had http header for that we can leverage http2 push and replace even components which state were changed as side effect.
React-Redux, Elm, Vuex doing this already. Just bake actions to urls and keep store on server.