It&#x27;s certainly lowered the barrier of entry for me, and I&#x27;m no web developer - my background is mostly back-end Java. Sure, I started out by making websites when I was younger, and a few of my jobs have involved a bit of front end, but I&#x27;d be surprised if there are many developers that don&#x27;t know the basics of HTML, CSS, and JavaScript.<p>Using web technologies to develop a GUI has been so much easier than learning a new toolkit, or even language. For one thing, some of the options you mentioned are OS specific. There are benefits to OS-native toolkits, but as a one-man team with a small project, the benefits are small and the time investment large. With Electron, I can build on Linux and release for Win&#x2F;Mac without any concerns.<p>Qt is the best option of those you mentioned, and I considered it. But I was never great with C++, and learning a whole new markup language (or being tied to Qt Creator) for the UI was an extra barrier for entry. And I&#x27;ve often found that Qt programs don&#x27;t look or feel right outside of Linux.<p>Personally, I find developing a UI on HTML&#x2F;CSS&#x2F;JS much easier than any desktop UI toolkit I&#x27;ve tried in the past. Updating the UI from the code, and calling code from the UI is s simple, because that&#x27;s what it was designed to do. And having a browser console makes debugging and trying things so much easier.<p>I was never a fan of using JS for anything but websites before, but I decided to give Electron a try and I&#x27;m a convert. Perhaps there&#x27;s enough of a speed difference between JS and native code that it would matter for more complex programs, but for my uses I don&#x27;t notice a difference, thanks to the speed of JS engines now.<p>Maybe from someone that&#x27;s starting with no coding knowledge would find Qt and C++ just as easy to pick up as HTML and JS, and certainly a C++ developer would find Qt a better choice. And sure, I don&#x27;t expect anyone to be able to build Photoshop on top of Electron. But there are plenty of programs that aren&#x27;t that complex.<p>While in theory I agree with not using the &quot;new sexy technologies&quot; for the sake of it, and &quot;using the right tool for the job&quot;, I don&#x27;t think that applies here. It works both ways, don&#x27;t stick with old technologies just because that&#x27;s what you&#x27;re used to. What specific benefits do you get from using one of those toolkits for a simple desktop program?