I'm not sure either make sense. So much of GUI programming is learning a particular toolkit. Especially in the case of Qt where it's an entire _runtime_--memory management, string types, threading, async/signaling, etc etc. This isn't even mentioning the hoops you have to jump through to compile a Qt program (if you're using C/C++).
These toolkits are inevitably on their way out. The future is the browser stack, loathe though I am to accept it.
As a tangent, it wouldn't be horrible if something like a browser was used as a window manager and UI runtime a la ChromeOS except with apps running in containers (and no bastardized Linux kernel and the restrictions that come with). This would have lots of benefits--the whole frontend benefits from all of the investment going into the web (including wasm) and the whole backend benefits from the investment in containers. Notably, packaging / dependency management, process management, log management, etc would all be much simpler/easier.
These toolkits are inevitably on their way out. The future is the browser stack, loathe though I am to accept it.
As a tangent, it wouldn't be horrible if something like a browser was used as a window manager and UI runtime a la ChromeOS except with apps running in containers (and no bastardized Linux kernel and the restrictions that come with). This would have lots of benefits--the whole frontend benefits from all of the investment going into the web (including wasm) and the whole backend benefits from the investment in containers. Notably, packaging / dependency management, process management, log management, etc would all be much simpler/easier.