unpoly VS remote-standalone

I really like the potential for sending minimal document elements, though it seems like these features should be built into the browser. Unpoly, for example, has its own entire reimplementation of fetch():

https://github.com/unpoly/unpoly/blob/4854c7ccb268890a9522c6...

Do any browsers have the early workings of a native web application sdk?

I published this article on Template Animation (aka DOM Templating) 12 years ago:

https://benkoworks.com/your-templating-engine-sucks-and-ever...

It fits nicely with this goal. My colleagues and I created a tool that allows HTML developers to work in HTML by compiling HTML using a Chrome extension, and then allowing developers to compile the same in their code platform of choice and operate on the DOM:

https://github.com/iaindooley/Fragmentify

https://github.com/iaindooley/fragmentify-js

Even if you're doing a SPA you can use this same method, by sending updates over the wire and doing the processing on the server. We created a standalone package that facilitated that by loading the initial page from the server then transparently allowing the server to send just the changes to the page and having them applied on the client side:

https://github.com/dgrinton/remote-standalone

The combination of "remote" and "fragmentify" and Template Animation/DOM Templating, in my opinion, would be a tremendous "retreat to move forward" in web development technologies.

Many years ago a colleague and I wrote a stand-alone version of a package for my own arcane php framework called Remote.

The idea was that you write in Web 1.0 and immediately get a Web 2.0 front end because it just updates what it needs to.

I still think this is the holy grail of frontends:

https://github.com/dgrinton/remote-standalone