developer.fyne.io VS Svelte

I would suggest having a look at https://developer.fyne.io/ for how to get started. For system tray documentation, you can have a look at https://developer.fyne.io/explore/systray.

Development information and documentation is available at https://developer.fyne.io/.

Don’t hold this against the team, it was my decision to write a book, the expectation was that some people prefer the written word in this form. Alongside the docs at https://developer.fyne.io and our library of videos and online conference talks https://www.youtube.com/c/fyne-io there should be enough for most to get the answers they need. If that’s not good for you join one of our chat channels alongside gophers on Slack, Discord or Matrix - there is usually a volunteer from the team ready to help out and answer questions.

Most of the complexity of Tree is the “collection widget” caching and re-use - which aims to be consistent with List https://developer.fyne.io/widget/list and Table https://developer.fyne.io/widget/table. You’re right though, another tutorial covering the ID relationship for building the data structure would be helpful - feel free to open an issue (or PR) on the site’s repo https://github.com/fyne-io/developer.fyne.io

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.

Volar originally was Vue3's language support tool for VScode (I don't know about other editors). By today, volar has become a language indipendent framework to create language tools. It might still be a bit early for the dev with skill issues like me to use it and build some tools, but astro and svelte already use Volar to create their language tools.