Linked by Thom Holwerda on Sat 14th Feb 2009 12:55 UTC
Permalink for comment 348963
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2008-12-26
Not to mention how coding for QT is just plain UGLY compared to objective-c, vala, c#, or pretty much anything else I can think of, well maybe, MFC is almost as bad as QT.
Qt code actually flows really well - I wouldn't call it ugly at all. It's a telling fact that PyQt ui code is not all too different C++ Qt ui code (to the point where PyQt documentation is pretty much a copy of the Qt documentation). Managing that in "writing to the metal" language like C++ is no mean feat.
The alternatives you present are proprietary/specialized languages for a small target group (ok, C#'s target group is large but still limited mostly to one segment of computing, Windows), while C++ is a standardized "universal" language that delivers pretty much the best performance on all platforms.
Regarding the choice of Gtk for chrome - the toolkit choice doesn't really play a big part here, it will use Chrome's custom stuff for almost everything. It's mostly about file selection dialog & the likes. I believe this is the same situation with Firefox and OOo.