scenebuilder VS Svelte

SceneBuilder, good luck!

Can't argue with that, but to me it seems that things have substantially deteriorated since desktop GUIs fell out of fashion. Maybe that tells you more about my age than about the state of the art, but in the 90's one could "learn" GUI programming in about 30min in a RAD tool by throwing controls in containers and implementing callback functions in "direct style" for the event (Qt , swing, Java/ScalaFX, Gtk, Forms, delphi, …), or do all that in code instead, with objects representing components and inheritance/OOP doing wonders to encapsulate state, expose a type-safe discoverable API, and offer customizability through members override. Entire generations of corporate monks made visually and functionally convincing business apps with VBA in an afternoon for instance.

Yes it does[1] and it works on Desktop, mobile and web.

JavaFX has SceneBuilder[2] which also fit the description but for some reason, it never caught on. Gluon seems to have that work not only on desktop, but also on mobile.

[1] https://docs.flutter.dev/development/tools/devtools/overview

[2] https://gluonhq.com/products/scene-builder/

JavaFX (Desktop) -> Use Scene Builder standalone from Gluon. https://gluonhq.com/products/scene-builder/

Additionally you can learn JavaFX for desktop applications. JavaFX with Gluon Scene Builder (https://gluonhq.com/products/scene-builder/ ).

SceneBuilder

Just run it from source until you figure it out

the technical decision how Svelte should treat self-closing html elements was hindered by Prettier:

Svelte

React has introduced measures like batching state updates, background concurrent rendering and memoization to tackle this. My opinion is that the best way to solve the problem is by improving their reactivity model. The app needs to be able to track the code that should be re-run on updating a given state variable and specifically update the UI corresponding to this update. Tools like solid.js and svelte work in this manner. It also eliminates the need for a virtual DOM and diffing.

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

Svelte is a powerful web framework that offers a fresh approach to building web applications. Its simplicity, reactivity model, and built-in features make it an excellent choice for developers looking to create efficient and maintainable applications. By following this guide, you should now have a good understanding of how to get started with Svelte and build your first components, routes, and transitions. You can read more about svelte on the official Svelte website.

Use .NET features (especially dotnet watch) as a setup for a client-side Svelte application, starting from a simple C# console app.