Username or EmailPassword
Linux user Tess Flynn joins us to follow up on the feedback from last week's episode about Xorg.
@jabjoe, XCB's the one, I didnt recall the name, but on the other hand. How can you convince projects to switch that are already using XLib? - It breaks compat with older unix's, for a nicer API (but still requires rewriting parts of the app that currently work). - A shame really.
@jjmckay, agree that this is more complicated then people give it credit for, while I didnt ever do Xorg development, my experience is that often making something simple for the user can end up being fairly complicated for the developer. When hardware compatibility is involved its worse.
@diego, maybe they have no idea but theirs is more of a user perception, nothing wrong with this but when outsiders (non Xorg core-devs in this case) speculate on a projects direction, I find it almost laughable.
Maybe the problem is the X11 api, maybe its the drivers, maybe its sloppy code??? - speculating on this without some understanding the xorg internals is stupid, better interview someone who knows what their talking about. Edited 2009-08-25 06:47 UTC
Thanks for looking into this,
For Blender3D we use X11 directly but only to setup the OpenGL context, pass on events & copy/paste, there are about ~2000 lines of xlib code in total.
We also have some crazy guys that still support Irix (and solaris but at least thats not EOL'd yet), not sure if this is supported without static linking, would need to look into that too.
While using Xlib is a total PITA to work with, its rare that it needs updating so theres not much incentive to switch.
The only thing that would make me interested in doing this, is if it was faster or somehow gave a better user experience.