Quote Originally Posted by wysota View Post
You can cut down the size of the libraries if you want to.
I'm aware of this, but I eventually got tired of rebuilding Qt to try and get the size down to minimum (disabling some things in qconfig causes compile errors sometimes - I assume because it doesn't remove everything properly every time), and then when I got something small that worked, I noticed later on my application didn't work as I was using things which were not built into release mode of library, and then you have to rebuild again. So now I just use full size library and complain about size

Quote Originally Posted by wysota View Post
That's not true. It is so only by default so that things work faster. If you disable Alien Windows, you get a native handle for every widget in your application.
Really? I thought the way Qt always worked (and has it was massively portable) was by drawing everything itself.

Quote Originally Posted by wysota View Post
Do you have any proof to back that up?
Proof as in benchmarks? No. However, I notice that via Spy++, Qt application receive message for every movement of mouse with new mouse co-ordinates, along with hundreds of hittest messages and various others. On the same app written for MFC, the application receive far fewer messages as a lot more is done by the OS. From that I came to the conclusion of "Fewer messages to process = Faster performance".

But like I said, I like Qt. It has disadvantages, sure, but those are worth it to get its advantages.