4 ms·
Every time I touch Qt, it feels more like Java than C++. Both because it has reimplemented everything and abstracted the OS completely (write once, debug everyw
by zokier 14y ago
Every time I touch Qt, it feels more like Java than C++. Both because it has reimplemented everything and abstracted the OS completely (write once, debug everywhere). And the memory use patterns seem similar too, Qt feels very lax on how memory is used, and seems to prefer heap allocations a lot.
Those are just superficial impressions, but while Qt is terrific GUI toolkit and set of libraries, the all-encompassing framework style doesn't fit to me.
- excuse-me 14y agoAn all encompassing framework is useful if you want cross platform - you can still have Createfile(Handle) fopen(FILE*) if you want with a bunch of #ifdefs. Most of it's own collection classes have been replaced with std:: versions. There is still QString but it does a lot more than std::string, especially if you need to be multi-lingual Signals/slots I like more than the boost equivalents. The multithreading probably is better in c++11
- rubashov 14y agoQt is what it is because in the 90s and much of the aughts they needed to implement loads of their own stuff for support across many compilers and platforms. That's not really true anymore and using their containers and smart-pointers and so forth is now really annoying. Anyone used gtkmm? That seems to be the one cross platform C++ GUI framework that doesn't try to re-implement massive chunks of the standard library and forsake modern C++ programming style and idioms.
- asdkl234890 14y agoEvery time I touch Qt, it feels more like Java than C++ I just wish they something as powerful as the GridBagLayout. No, QGridLayout is not it.