@andik70
Well following points: - Qt did a lot of things their own way (which was necessary using C++98 or so), but which are not needed anymore. Qt cannot follow this language development, since this would break backward compatibility. So joint progress would be difficult. - Also Qt is a product. If you want a commercial license you need to pay. Also on the webpage under embedded development, a plus point is 'avoid legal risk'; legal risk from whom? I find this too threatining. Since I agree one can use Qt, I find contributing to the well beiing of a company is a bit different then contributing to a computer language.
@Sakari_369
Yeah I seriously considered using Qt with my project, and probably would still use it if was building a crossplatform UI application. But for example in OpenGL or game engines, no way I would like to bring in Qt and it's dependencies, and odd ways of using C++ compared to current C++11 and C++14 standards :P
@origamibulldoser1618
Why would anyone want to write UI in Qt, though? Why choose the decidedly worst language for rapid development to develop and maintain a UI? And yes, UI development sucks balls to begin with: "Can I get the icon in corn flower blue?" -Sincerely, Your Team Leader / Boss / Whatever
@detectivemarkseven