> it's also about acting like native apps. Slack feels like a native app. VS Code feels like a native app. I'm not sure if you're arguing as if this is powered

> it's also about acting like native apps. Slack feels like a native app. VS Code feels like a native app. I'm not sure if you're arguing as if this is powered by some sort of black box powered magic no one could understand? Electron is just a website, the Node APIs and a couple of facilities from Gtk, like menus. You have access to these things or equivalents in QML. You would know this if you had bothered to learn what it actually is. > I spoke to Qt, and QML is literally the "Qt Modeling Language". It renders elements using Qt Quick. I'm not entirely sure how switching the mechanism for defining your Qt interface from code to a markup language invalidates my point. You're literally searching for a couple of terms in Google half-guessing what some of the words mean and thinking you now understand Qt. Qt is a big set of libraries. Qt widgets is a traditional widget toolkit that powers things like VLC, Google Earth and VirtualBox. It's software-rendered and exclusively programmed through C++. It's a subset of Qt. QtQuick is a different subset, that is powered by a 3D-accelerated scenegraph, can be programmed from QML, JavaScript and C++ and has primitives both for native-like widgets (QtQuick Controls 1) and simpler, more performant primitives (QtQuick Controls 2) that allow you to do everything you can do in a website with the DOM and CSS. You can mix and match subsets, which is part of the beauty of Qt, but each of those have completely different purposes. > It's unbelievable to me that you responded to my post about how the most popular Qt apps are the one with the least Qt interface, with an example of a Qt app you wrote (using QML) that literally has no interface. Fine. Have a VS Code prototype just for you, made in under an hour: https://i.imgur.com/RPr6VMS.png https://i.imgur.com/RPr6VMS.png Some of it is functional, like tabs and menu. Sidebar and file tree is mere decoration waiting to be connected to logic. But there's your magical "native feel" interface in QML. Ah, and if you were to actually complete the prototype, you could probably rip off the rich text editing component from the Kate text editor (written in Qt widgets) and still be able to use it from QtQuick. Meaning you get syntax coloring, auto complete and many other things for free, if you wanted to. Here's the code: https://gitlab.com/mixedCase/poc-qml-vscode https://gitlab.com/mixedCase/poc-qml-vscode If you have the dependencies installed, you build it with qmake -o Makefile qml-vscode.pro && make Enjoy.