3 ms·
> They're both C++ though. I’d argue that Qt API is pre-C++98, ie. pre std template library. Qt uses its own classes (vector, string, etc) instead of std templ
by smallstepforman 4y ago
> They're both C++ though.
I’d argue that Qt API is pre-C++98, ie. pre std template library. Qt uses its own classes (vector, string, etc) instead of std template library. Even the MOC can be eliminated with the STL. Its an ancient API which is separate from modern post C++11. They’ve tried adding some STL and C++11 concepts, but they have millions of lines of legacy code to support, so its just more layers and bloat.
- sho_hn 4y agoYou're not completely wrong, but I think this overstating things by a lot. I'll grant you the containers for example, but you can generally use STL algorithms with them. And plenty of old ways of doing things have left modern Qt-based codebases and moved to more modern ways of doing things, including a fair amount of moc macro usage (and yes, you can remove the moc these days, but it has different perf characteristics - cf. the verdigris project). The community around Qt is pretty active at adopting modern C++, e.g. imho https://github.com/danvratil/qcoro https://github.com/danvratil/qcoro is leading work. I'm glad that folks clamor for keeping things fresh, but every 30 year old project is going to span a few minor revolutions along the way.
- pjmlp 4y agoIt is still C++ and in many aspects, much better than the current trends on the standard library design. Also, alongside VCL/Firemonkey, miles ahead of any C++ UI framework produced by Microsoft, WinDev just has no taste in doing GUI tooling for C++ developers.