Linked by Kroc Camen on Thu 20th Aug 2009 09:43 UTC
Podcasts What else would we talk about other than the massively [popular|controversial] article about X.org last week. We try and address a number of concerns about the article and common lines of reasoning / misunderstanding. Lastly, we move onto something completely different with topics on Google Chrome on Linux, IE6 and the two details we know about RockMelt: Rock. Melt.
Thread beginning with comment 379638
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: independence from X
by ba1l on Thu 20th Aug 2009 12:25 UTC in reply to "independence from X"
ba1l
Member since:
2007-09-08

Qt's raster back-end runs faster on X as well in most cases. The major drawback is increased memory consumption, as each application has to maintain it's own glyph cache for drawing fonts, rather than relying on the X server to do it for them.

Oh, and it completely kills network performance, of course.

Obviously the ideal would be to use OpenGL for everything. Qt's OpenGL back-end beats the raster engine (often by a wide margin), but comes with it's own share of problems.

Reply Parent Bookmark Score: 3

RE[2]: independence from X
by PlatformAgnostic on Thu 20th Aug 2009 22:12 in reply to "RE: independence from X"
PlatformAgnostic Member since:
2006-01-02

It doesn't have to be that way... you could put the glyph cache in a central process and share the memory containing the rendered glyphs with other processes. In Windows the glyph cache is one of those things that's kept in the kernel session space.

Reply Parent Bookmark Score: 2