Pyract: a new way of writing Gtk+ applications

So this recreates the <i>entire</i> scene graph whenever the UI needs to be re-rendered? What happens when you use this in a complex application with lots of different nodes that needs to be updated frequently? Think a midi tracker &#x2F; DAW &#x2F; video editor, where it&#x27;s common to have a vertical bar that moves across the screen indicating the current section of audio&#x2F;video being played. Is this still suitable for that sort of application? I get that it&#x27;s doing diffs and not actually re-rendering <i>everything</i>, but how heavy is the call to create each node?

This is similar to what React.js or Vue.js does on the browser. I always thought of this, very nice to see it running. I worry about the following.. 1. How we do complex objects like Trees and Tables? 2. How efficient are these Native nodes over DOM nodes in Browser?<p>I always wonder between Native vs DOM.

For a quite similar approach of observing&#x2F;binding variables to GUI objects, have a look at Qt&#x2F;QML.

Certainly much nicer than the traditional way of doing this :)

This is great! Is there anything similar for developing macOS apps?