You also forget:<p>- There are far fewer native components, leaving  accessibility down to the developer of the app and making it nonexistant.<p>- Platform integration is impossible, which means there is no way for the framework, for example, to create widgets differently on OS X, Windows or Linux (these platforms have many different conventions)<p>- Theming globally becomes impossible. If you want to write a dark theme for your desktop, you go from writing a theme once for GTK and once for Qt to once for each and every app you run. Uuuurgh.<p>But only supporting one rendering engine, yay! Much better than the 6 different engines we have to support in Qt (huh?).<p>And having access to all the latest JS additions! ... that were copied from other languages you could develop desktop apps in, because JS is a terrible hack.<p>And relying on native Node.js modules, yay! As opposed to native modules for literally every other better language out there.<p>I&#x27;m not sure what you&#x27;re actually comparing this workflow <i>to</i>. Maybe one day writing HTML apps will be great, but today is not that day. Today, writing HTML apps is only beginning to be an idea that doesn&#x27;t <i>completely</i> suck. But for the user, it does massively suck. Massive apps that ship their own copy of webkit&#x2F;blink&#x2F;whathaveyou, with security flaws that won&#x27;t get patched, disgusting performance on low-end hardware, atrocious battery usage and decades of UX knowledge thrown out of the window just because the app developer doesn&#x27;t have the knowledge to see it.<p>I don&#x27;t look forward to this. And I&#x27;m younger than you.