Problems with X.org and incompatibilities with in-house software

[Corbin Simpson]

On Sun, Feb 28, 2010 at 8:13 PM, Richard Brown <rbrown1445 at gmail.com> wrote:
> Alan Coopersmith wrote:
>> On the client side we've pretty much preserved API & ABI compatibility,
>> even
>> when that required major gyrations for the XCB effort - while we
>> encouarage
>> migration to the new XCB libraries, it will be a couple decades before
>> libX11
>> fades away.
>>
>>
>
> I do not expect xlib to ever go away. There is so much written for it, its
> sort of pointless to refactor apps "because we can". If one makes a new app,
> XCB may be a good choice, when it is mature. I am not sure what benefits XCB
> has however. It could be as well, the way things often go, someone will
> forget some needed feature in XCB and Xlib may end up being a better choice
> in some situations. Ive often seen things like that happen. Case in point .,
> i upgraded t KDE 4.0. The new Konsole does not take the escape codes for
> setting the title bar with program name/path name i have sent by tcsh precmd
> and postcmd. I deleted KDE 4 and went back to KDE 3. Someone didnt
> understand the importance of this and didnt include this. KDE 4 for me was a
> downgrade, it actually regressed.

XCB cannot possibly omit any protocol information because of the way
it's crafted: It is directly generated at build-time from descriptions
of the X wire protocol. It also is far more intelligent about avoiding
round-trips to the server and such. That said, people generally wait
until the very last minute to switch away from legacy software, so
it's not like people are switching in droves.

-- 
Only fools are easily impressed by what is only
barely beyond their reach. ~ Unknown

Corbin Simpson
<MostAwesomeDude at gmail.com>