The Wayland Situation: Facts About X vs. Wayland (Phoronix)
The Wayland Situation: Facts About X vs. Wayland (Phoronix)
Posted Jun 12, 2013 21:02 UTC (Wed) by k8to (guest, #15413)In reply to: The Wayland Situation: Facts About X vs. Wayland (Phoronix) by farnz
Parent article: The Wayland Situation: Facts About X vs. Wayland (Phoronix)
(Log in to post comments)
The Wayland Situation: Facts About X vs. Wayland (Phoronix)
Posted Jun 14, 2013 16:21 UTC (Fri) by farnz (subscriber, #17727) [Link]
Pretty much that, plus some pain where XLib did multiple X roundtrips in one call (e.g. XQueryTree), and you now have to manage multiple request/reply pairs. There's also a small and shrinking area of pain where an extension is XLib-only, and you have to use XCB/XLib interop.
Additionally, the problems XCB fixes aren't visible if you do what most people do and use a local X server - they're only a pain if you want to use X over the network. So, for most developers, why port to XCB when you get easier, cleaner code with XLib?
The Wayland Situation: Facts About X vs. Wayland (Phoronix)
Posted Jun 14, 2013 16:52 UTC (Fri) by dark (guest, #8483) [Link]
We might need a library that makes using XCB easier :) And I don't mean one that tries to be a layer on top (that would be libX11 all over again), but a library that provides tools for managing multiple related xcb calls, helpers for useful patterns like prefetching, and tons of convenience functions for common operations.Unfortunately I probably wouldn't work on such a library because I'm not involved with any X11 based code anymore.
The Wayland Situation: Facts About X vs. Wayland (Phoronix)
Posted Jun 15, 2013 1:32 UTC (Sat) by hummassa (guest, #307) [Link]
it's called Qt. :-D