this post was submitted on 04 Mar 2026
24 points (73.1% liked)
Programming
25936 readers
312 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I have no dog in this race as far as Claude is concerned, but this is pushing a false dichotomy. Not using, say, WinForms or something, because it's too limiting or because you don't want to make a unique UI for every platform, doesn't have to mean strapping an entire web browser to your frontend, there are plenty of other options.
The reason frameworks like Electron are popular is that we've spent a long time hammering a square peg into a round hole and there are now a whole bunch of tools for designing on top of web technologies and a lot of designers with experience with those tools. And of course, the fact that code can be reused between the web app and the desktop app helps too. But it does have a performance cost. The fact that you can have poorly performing and bloated native UIs too doesn't change that no matter how well-optimised your HTML+CSS+JS is, you can create something of the same complexity that is faster and leaner using native widgets. And when people opt for the desktop app instead of web app, they typically want something that performs better than the web app.
I mean, Qt for example?