Nothing wrong, much less "vastly inferior" with Qt containers - their performance is on par with std containers, and Qt containers use is actually less verbose and much easier to use. std containers are overly verbose, pretty much all operations require iterators.
He is right about the pricing though. It needs to be cut at least in half to become reasonable.
it's still for small business (which I'm not),
Personnaly a small Qt logo on the front (top left) + a big back design on a black t-shirt (2016 edition).
For the RPi : Mainly it's the toolchain, ideally, having it as a target like Android (being able to d/l it from Maintenance Tool) would be awesome (and would save a lot of time, instead of having to handbuild it for cross-compile).
Basically making things simple and easy.
To me it sounds like you are pretty much covered (iOS aside).
The main idea with LGPL is to let the user use and modify the product. Static linking in itself is not bad if the developer is ready to provide the objects and toolchains (and scripts and whatever else is needed for the user to work on the product).
The deployment tools do have their problems, I agree with that. And when I play with Qt, I use the defaults. But then again, I definitely am not a proper developer.
Can i use the opensource version of Qt Creator under the LGPL to make closed source software and sell it, as long as the Qt libraries are dynamically linked?
I presume you mean the LGPL version of Qt (the libraries), not Qt Creator (the IDE)? The Qt Company is happy with what you have described: http://www.qt.io/faq/
"The LGPL allows you to keep the source code of your application private as long as it is “work that uses” the library. Dynamic linking is usually recommended here."
Note: Nobody really knows the legal answer to this question from a broad LGPL point of view, because this has never been dealt with by the courts before.
If i use MinGW is anything i compile with it then restricted to the GPL
No. The tools are GPL, but your code doesn't have to be GPL.
If i use LLVM (not tried it yet but seems promising), will i have to compile Qt Creator, and the Qt framework with CLang(++) in order to then compile my Qt projects with CLang?
You don't have to compile Qt Creator.
You might have to compile Qt... I'm not sure, but I think the GCC version of Qt is compatible with clang.
i can then use the same setup of Qt creator/framework as well as the same compiler, meaning i then don't for instance use MSVC for windows and gcc for linux but can use LLVM for both.
Frankly, this has zero impact on my development workflow. I use MSVC on Windows and GCC on Linux, but my code can be shared between the two machines without any modifications, and the way I use Qt Creator is exactly the same on both machines.
this ne peut pas être utilisé dans main donc vous devez être en train d'essayer de faire quelque chose d'interdit par le C++.
Pour ce qui est du prix cela dépendra de comment vous désirez déployer/commercialiser votre travail. Vous trouverez "ici":http://www.qt.io/download/ une liste des prix courants. Pour plus de détails, le plus simple serait de contacter The Qt Company au travers du formulaire accessible en bas de la page.
Petit détail pratique: la langue officielle de ce forum est l'anglais donc je recommande de l'utiliser pour la suite