If you work in software development you ought to know that "just use X" is often not an acceptable solution for many reasons. Quick example: maybe you develop a windows heavy client with a linux backend and want to test it locally. Then you have a choice to have either (relatively) poorly performing Windows VM or linux VM. As backend is usually way lighter and your IDE is probably Windows native too, you should run this on Windows.
Why not just run inside KVM on Linux, and why use a bloated windows framework and toolkit? Qt is a great example of a cross-platform framework that doesn't require a lot of dependencies. However, you could also just build a PWA. If you're going to use bloated proprietary frameworks, why even use Linux at all?
I hope this is sarcastic because it illustrates my point perfectly. Qt is a great cross platform framework but maybe you are not developing a cross platform application? Maybe you actually prefer native look and feel (I do for example). Maybe you are developing an app that must be published on the Windows store or work in Kiosk Mode (all of which require you to build on top of the native UI framework).
> If you're going to use bloated proprietary frameworks, why even use Linux at all?
You could as well rephrase your question as "Why not use the most appropriate tool for each part of the software?" Linux servers have the advantage of being supported by all major providers (including Microsoft), they scale well, have good security, have low footprint...
Also as much as I dislike Windows I must say that their UI frameworks are not bloated and arguably work better than cross platform solutions. You mentioned PWA's which come with an enormous bagage (e.g.: they are throwing native look and feel completely out of the window).
I think this is what the parent means by "just use X". You are saying to someone to change their whole development environment to Qt. (I like and have developed a commercial product in Qt)
