Linked by Thom Holwerda on Wed 14th Jan 2009 09:54 UTC, submitted by Almar
Thread beginning with comment 343623
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
I certainly hope there's a move to trash a lot of the Qt infrastructure and replace with stl and other already available good quality 3rd party libraries.
You can use stl with qt, and other 3rd party libraries. Those qt counterparts exist in qt for a reason. Mostly, it is the price to pay for being truly cross platform, especially so if you realize that gcc is not the only compiler people use. Also, most of the qt API QtXML is way more advanced and easier to use than the alternatives. Heck, some don't even have a viable alternative, like phonon and webkit.
And get rid of MOC while we're at it too.
And? use the pathetic C++ introspection thingy? And use the ugly signal/slot libraries out there?
No thank you. I would stick with moc.
And get rid of MOC while we're at it too.
And maybe get rid of Designer and hand-code our UIs again? Get rid of QObject parent-child relationships and manage memory manually?
Layers of abstraction help the developer deal with complexity. Just because you don't understand it, doesn't mean it's bad.
I certainly hope there's a move to trash a lot of the Qt infrastructure and replace with stl and other already available good quality 3rd party libraries.
STL? Good quality third-party libraries? Boost, per chance?
So you want to destroy C++ programming again for everyone?





Member since:
2006-01-06
Now that Nokia has decided to open Qt that means that this "borg like" model of qt which smacked of developer lock in and not invented here syndrome can come to an end.
I certainly hope there's a move to trash a lot of the Qt infrastructure and replace with stl and other already available good quality 3rd party libraries. And get rid of MOC while we're at it too.