Re:X11 Window System Turns 25 Years Old
by vidarh on Saturday September 15, 2012 @04:13PM
(#4527156)
I really don't think this has anything to do with it. Yes, there are complexities with X, but nobody writes serious applications targeting X. You target a toolkit. And the toolkits have effectively abstracted X away for many years. So well, in fact, that both GTK and QT can run fine with other backends (including a web browser for GTK, as well as DirectFB and Wayland).
No normal application developer "have to deal with a network protocol". Even if you write code directly against Xlib that is largely transparent to the developer.
Performance was an issue until XRender and DRI arrived around 2000. It has not been an issue for years.
Incidentally, one of the reasons Wayland is becoming so attractive is exactly because so little of what X was traditionally is actually being used any more in most setups, since XRender and DRI combined means most apps does all or the vast majority of rendering client side, and the server is largely left as a resource manager and compositor and not much more.
No normal application developer "have to deal with a network protocol". Even if you write code directly against Xlib that is largely transparent to the developer.
Performance was an issue until XRender and DRI arrived around 2000. It has not been an issue for years.
Incidentally, one of the reasons Wayland is becoming so attractive is exactly because so little of what X was traditionally is actually being used any more in most setups, since XRender and DRI combined means most apps does all or the vast majority of rendering client side, and the server is largely left as a resource manager and compositor and not much more.