3 ms·
Here's an explanation of those needs: Gtk to Qt - a strange journey https://www.youtube.com/watch?v=gGZyVSOnqm0 https://www.youtube.com/watch?v=gGZyVSOnqm0 "P
by Sammi 7y ago
Here's an explanation of those needs:
Gtk to Qt - a strange journey
https://www.youtube.com/watch?v=gGZyVSOnqm0 https://www.youtube.com/watch?v=gGZyVSOnqm0
"Presenter(s): Dirk Hohndel"
- albertzeyer 7y agoIt seems this was posted a few times to HN already (I just posted it again: https://news.ycombinator.com/item?id=20746962 https://news.ycombinator.com/item?id=20746962). Quite interesting. Some of the messages: * Their GTK code became very fragile, such that they did not wanted to touch it anymore, and could not implement new features. * The GTK community was/is not helpful. * The Qt community was/is very helpful. * Qt documentation is much better than GTK. * The Qt frameworks has more to offer (basic data structures, etc). * CMake is much nicer and easier to understand than just raw makefiles (but somewhat unrelated to Qt vs GTK). * The model and view system/framework in both Qt and GTK is somewhat/completely broken. * Qt Creator makes live easier, compared to Emacs (at least for C++/Qt development). * Qt is nicely encapsulated, in contrast to GTK.