nw.js VS Svelte

> FUSE drivers are slow, but "wildly slow" is an overstatement.

I can confirm this, I've played RPGMaker M{V,Z} games natively by swapping out the copy of NWJS¹ it shipped with and running it through a CIOPFS² mount.

1: https://nwjs.io/

2: https://www.brain-dump.org/projects/ciopfs/ / https://github.com/martanne/ciopfs

Go to this page to download NW.js https://nwjs.io/.

(Step 7 will not be necessary once https://github.com/nwjs/nw.js/issues/5769 is completed)

The support for WebGL in NW.js on Linux has been broken since NW.js 0.72.0: https://github.com/nwjs/nw.js/issues/8043

In addition to the other options here you could look at nw.js

I don't think you can access it by default, but crosscode runs on [nw.js](https://nwjs.io). I know there is a way to get the chromium devtools to open, but I haven't been able to.

or browse the NWJS home page at https://nwjs.io/

If windows is your target, you can use .hta If Ubuntu is your target, you can use GJS If Mac is your target - well you are going to use something like QT if you need total control or nwjs.io

BrightSign has pretty good docs that explain this. There are a ton of similarities to running NW.js, so it might make sense to check that out as well (https://nwjs.io/). DM me if you have more questions. My team and I have built a few Node applications for BrightSign players.

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.