A very underrated flippening:

It feels like these days when open source software devs make software with UIs *that runs locally*, a lot of the time the UI is built *as a webpage* and you access it by going to localhost:3030

I actually like it, much lighter than an Electron UI for example, and more portable. The web browser is the ultimate compatibility platform.

Why move it local in that case? What’s the benefit over deploying it on a high performance server and accessing it remotely?

Live in Colorado; TechnoGeek; Proud mother of a fey creature in the form of a cat; part time vegan, part time meat connoisseur; walker of edges.

Who's gonna pay for the high performance server? With the local server the user pays for the compute. Also nice that data can remain local.

Besides what @deanpierce.eth and @thetechnocrat have said, IMO native toolkits are harder to develop. Even if you use a multi-OS GUI library, you still have all OS interaction. In the end that leads developers to release "MacOS only" or "Windows only". You can see why many Linux users are liking the web UI trend.

Why not take advantage of the enhanced graphics and capabilities if it’s only going to be ran locally? The advantage of web based interfaces is remote interaction without local installation. Even using something as light weight as TK can give a better experience and more powerful interface.