Qt 5.0 on Linux is using the X C-language Bindings rather than Xlib since that's what is generally favored these days for communicating with the X.Org Server. On Qt4, Xlib was supported. Just one day after there was the controversial freelance article about Mono being desirable for Linux, another developer is sharing his freelance views on a separate project. Steven Starr as a Linux desktop developer wrote into Phoronix with his views (well, it's more along the lines of a brief rant but does spark a valid point) on Qt5 about the change.
I wonder about Qt developers some times.
Qt5 is OpenGL based right, well XCB is a requirement on Linux now, it wasn't on Qt4. And XLIB isn't supported.
Let me throw out a quote from the XCB devs.
XCB-GLX only communicates with the X server, it does not perform any hardware initialization or touch the OpenGL client-side state. Because of this XCB-GLX cannot be used as a replacement for the GLX API. To use OpenGL in the X Windowing system, one must use the GLX API, and the GLX API is closely coupled with Xlib. As a result, an OpenGL application on the X Windows must use Xlib and thus can't be done using only XCB. [Citation]So what does this mean?
It means that they're forcing us to install and use XCB that doesn't support Hardware Accelerated Graphics using your ATI/NVIDIA binary drivers. And it ends up reverting back and using XLIB/GLX anyways.
Qt5 + XCB = Low Level Crippled API Wrapper for a Higher Level Fully Functional API.
If you ever wonderd why KDE4 and Nvidia cards are constantly breaking theres your answer. Because some stupid fuck thought XCB was cool because someone else told him it was.
The reason I am soooo pissed is because I have been writing a new Qt Desktop Environment for the last 1-1/2 years and Qt devs broke it by removing the QX11 API's. And my new desktop is blazzzzzzing rubber melting FAST!!!!
Has Qt5 with XCB caused problems for you? This isn't a Linux-specific problem but any Qt platform using X. Share your thoughts in the Phoronix Forums. Should you have any other freelance article to share with the Phoronix reader base, feel free to contact Phoronix.