Re: [dev] Wayland vs X11

From: Silvan Jegen <>
Date: Tue, 2 Aug 2016 22:54:43 +0200

On Tue, Aug 02, 2016 at 10:16:06PM +0200, FRIGN wrote:
> On Tue, 2 Aug 2016 22:08:08 +0200
> Silvan Jegen <> wrote:
> > Since Wayland is only a protocol, as long as both the client and the
> > server follow it closely enough both the clients and the server will
> > be happy. What is crucial is that the protocol is minimal and strictly
> > defined however. I am still cautiously optimistic that this is and
> > will be the case...
> It's not only about client-server interaction, it's about how you for
> instance should capture input in a compositor. You could use libinput,
> or a gazillion other libs out there with different levels of device
> support. I can already see the bug reports because this and that
> joystick, touchpad, whatever does not work in a specific compositor.

The Wayland protocol deals with input as well so as long as the clients
speak it, they are golden. libinput is supposed to make input handling
uniform on all Wayland compositors and can also be used on X11. I am
not sure whether Joysticks/gamepads are handled in it though.

> And even clients have to do their own font-antialiasing. Sounds like a
> lot of fun! Please stop repeating the propaganda spread on the web,
> Wayland is not DoA without reason, and there is also a reason why
> nobody uses it nowadays other than to play around with it. It's a

The rumors of its death are greatly exaggerated... Sailfish OS has been
using Wayland from the start and Fedora wants to make Wayland the default
for their next release (I wouldn't count on it).

> horrible mess and the wayland devs expect us to boil the ocean without
> any clear benefits at hand.

Wayland is supposed to give us a "tear-free" desktop at least... :P


Received on Tue Aug 02 2016 - 22:54:43 CEST

This archive was generated by hypermail 2.3.0 : Tue Aug 02 2016 - 23:00:13 CEST