unpoly VS knockout

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?

The approach is not new, essentially a variation of Knockout, Alpine, and similar "JS-in-HTML" approaches.

SolidJS and Tauri form another potent combination for creating performant, lightweight, and secure experiences. SolidJS is a reactive UI library that is similar to Svelte in the way it compiles away reactivity and updates the DOM directly, but it also incorporates a fine-grained reactivity system reminiscent of libraries like Marko, Knockout, and MobX.

People act like Signals are a new discovery. KnockoutJS was using them 13 years ago and other libraries used them before that.

Knockout JS is a Javascript library which uses the MVVM pattern to bind data to certain DOM elements. Within Magento, we usually define a View-Model (which is a .js file) and a Template (which is a .html file), and the data in the template file is bound to the view-model, meaning whenever the data in the view-model changes, the template file changes too.

I still use Knockout[0] for almost an identical experience.

0: https://knockoutjs.com/

One of the first uses of this concept was in knockout, which used the same function with and without arguments for write/read access.

To do this, use a Javascript library called knockout.js

You could use a JavaScript framework called KnockoutJS which uses the MVVM pattern.

Magento is built with PHP. A good understanding of PHP is generally enough to perform different development tasks such as building modules. However, developers often need to work with libraries like Knockout.js and Less when developing themes.