Caliburn.Micro VS knockout

It works with ActivateItemAsync but I don´t know if there is a difference that I should be aware of ? They seem to be a bit slow with updating the documentation so I´m a bit nervous about what else might not be updated yet.

The programming model reminds me of Rob Eisenberg's older attempts at building UI toolkits ([0]). I don't recall if that was fully async or 'just' using a coroutine/generator-style approach, but it feels similar.

I'm not sure the complexity of doing everything using async constructs is worth it, though. Large-scale UI's built in Qt or Javascript are mostly single threaded anyway, but it's still worthwhile to explore so kudos for that. Looking forward to seeing how far you get.

[0] https://github.com/Caliburn-Micro/Caliburn.Micro

Vanilla WPF has a lot of boilerplate and verbose binding expressions. I'd check out an MVVM library like https://caliburnmicro.com/ which has tons of convention-based features and helps maintain the "screens" in your app.

Your UI needs to bind to something that can programmatically notify it about changes, we call these things View-Models. Usually View-Models implement INotifyPropertyChanged interface (another key interface is INotifyCollectionChanged that is responsible for notifying collection views that number of items is changed and they need to update the UI accordingly). You can do that (the implementation of the interface) manually or use some library to do that for you just to cut some boilerplate code (e.g. ReactiveUI + Fody or Microsoft.Toolkit.MVVM or maybe even this or this).

I haven't done WPF/XAML stuff in years but I really liked Caliburn Micro, largely because of the convention-based auto-binding.

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.