I think the main reason that's a commercial offering is that developers of proprietary software like shipping binaries instead of human-readable QML files.
So you're saying there are projects where I cannot use Qt? The fact is, there exists projects that do not have the option of using Qt without paying for expensive licensing. Such projects should at least consider using Electron which might have significant non-technical advantages for them.
It is cool that what many consider to be the best commercial desktop GUI is also open source, I will admit that much. Still, we shouldn't complain too much when many projects choose to use Electron, it's licensing is just so much more permissive which is a significant advantage for many projects.
"I don't want to pay for software, so here take a bloated browser as fake native app".
I don't think QT and Electron are architecturally equivalent.
Electron uses components that are under LGPL (Chromium for instance) so it's basically exactly the same license questions than with Qt.
You can absolutely use it for free in any project, as long as you conform to LGPLv3.
Regarding JS: You're not supposed to write more than glue logic in JS - well, that's the practical experience. For some reason, the Qt company recommends more JS use than that.