Linked by Thom Holwerda on Thu 13th Dec 2007 18:27 UTC, submitted by SEJeff
Permalink for comment 290582
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/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2005-07-08
The problem of GTK is that it's over-engineered. Conceptually, everything is ok. Every behaviors of the toolkit is well thought. However, the end result is much less exciting. A simple resizing operation causes a zillion fonction calls. Most GTK theme engines are unacceptably slow (the fact that they are almost all based on Cairo now is one of the causes for this). In a corporate environnement, I think people can live with that. For the rest of the world, I think it's not something you want. I have 2 computers here, one running XP and one running Gusty, and I see a huge difference between both setup even when doing the same exact task. For example, SWT/Windows is so much faster than SWT/GTK. Using Eclipse on Windows is so much more enjoyable than using it on Linux. Honestly, having Gnome, Evolution, Firefox, Eclipse and OOo running at the same time isn't something pretty even on a high-end computer. I know we can't blame GTK for everything but it doesn't help.