Linked by Eugenia Loli-Queru on Fri 10th Aug 2007 02:53 UTC, submitted by J. M.
Thread beginning with comment 262607
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
RE: What a Load of Rubbish
by richmoore on Sat 11th Aug 2007 11:54
in reply to "What a Load of Rubbish"






Member since:
2005-07-06
I just wonder if people commenting on this thread are actually reading some of the better comments around here. Those of you talking about X being the main bottleneck haven't got a clue what you're talking about. In reality, X does very little, which is the way it was designed (it didn't specify a toolkit for a reason). The bottlenecks are elsewhere, and the biggest is how the toolkit manages this and what it pushed to the X server. Motif didn't seem to have this problem, as ugly as it looked and as bad to program as it was.
Options such as creating a new, separate, and incompatible, X server are just so stupid it isn't believable. This isn't going to be helped in X for some time, and even then, the biggest bottleneck is still how the toolkit goes about doing things. XCB, as I understand it, is a layer below Xlib, so doing various things directly with XCB can speed things up (and Trolltech may already be doing it), but it's not a panacea.
Apparently, if Trolltech fixes an awful lot of things in Qt then they're doing it all wrong because they should be fixing things in X. What an absolute load. What do you expect them to fix? Also, you have to take into account that this has to benefit cross-platform as well. If Trolltech does all it can to alleviate problems in Qt, and other parts of a system are improved along with it, then we should be in for a substantial improvement, shouldn't we?
I don't know what it is, but all this 'fix it in X' stuff just sounds like some thinly veiled explanation as to why GTK, and Gnome, is just so particularly bad on this front. Attempting to solve this with Compiz, or relying on hardware acceleration to minimise the effect, simply isn't any solution at all and really is a 'hack'.