Linked by Thom Holwerda on Wed 20th Oct 2010 22:22 UTC, submitted by vivainio
Thread beginning with comment 446376
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Technical superiority to GTK
by Neolander on Thu 21st Oct 2010 17:48
in reply to "RE: Technical superiority to GTK"
Trying to write a GTK+/GNOME app can lead to multiple coding styles, multiple API styles, tonnes of dependencies, and so on.
It's the different between using an IDE for coding, and using a mishmash of editors and command-line tools.
It's the different between using an IDE for coding, and using a mishmash of editors and command-line tools.
Not sure it's a good comparison. In some cases (e.g. when you really need fine-grained control on the compilation + linking process, like in kernel development), going text editor + command line is just the best option. In other (arguably most) cases, it's IDEs which rock. One should use the right tools for the right job.
On the other hand, I can't think of a situation where tons of dependencies with various coding styles could be a good thing.
Edited 2010-10-21 17:51 UTC




Member since:
2005-07-11
The nicest thing about QT is that it's one framework, one coding style, one set of APIs, one environment, one dependency.
Trying to write a GTK+/GNOME app can lead to multiple coding styles, multiple API styles, tonnes of dependencies, and so on.
It's the different between using an IDE for coding, and using a mishmash of editors and command-line tools.