3 ms·

> I can write one using Qt, EGUI, etc (Or many other options), and it will just work on Windows, Mac, Linux/Wayland, and Linux/X. This is hard to square with t

• d-us-vb 2mo ago
  I suspect the u ubiquity of electron persists more because maintaining both web and desktop interfaces is somewhat simplified, and as a corollary, you don’t need a separate JS and C/C++/QML team. Qt has gotten pretty good, but JavaScript and typescript are easier to hire.
  • pjmlp 2mo ago
    Pay for cheap labour, get a cheap product. I thought Claude could do anything nowadays.
  • bionade24 2mo ago
    QML is a Javascript Superset
    • d-us-vb 2mo ago
      But it runs on Qt, which is most certainly not.
• rtpg 2mo ago
  I think Qt is a bit different here because of Qt Quick etc but I've tried using "native" GUI frameworks a lot and ultimately the web DOM model is pretty nice for iterating easily. Querying into the DOM and working off of that means you're not futzing about holding onto a bunch of component references for the one thing you might need later on. Web layout is also pretty easy to just get right, native GUI frameworks have a different kind of layout model that is not as amenable to "arbitrary" data (at least at first blush). the reactive programming model also works quite well. While there are native GUI frameworks that lean into reactive programming, they tend to be doing a bunch of weird stuff that cause other issues. And at the end of the day, when you package something like a Qt app it still often ends up being quite chunky. In the end tho... the simplest thing is if you do web stack you get a web UI _and_ your "native" GUI in one go. Build things once, not twice. Hard to argue against that when that's presented.