Gregory's Server
I quite wish wayland wouldn't be compared to systemd so much…
Wayland is an evolution from X11 by it's own developers and pretty much all desktops environments involved.
Migration to it can be pretty gradual and smooth, in fact you can still just keep using Xorg/TinyX/… without added issues, just bitrot starting to appear because of new hardware.
Meanwhile Systemd is pretty much one-sided and it's also an implementation that forcefully shoved itself into the ecosystem.
It broke a ton of things and still regularly breaks things.
Wayland is an evolution from X11 by it's own developers and pretty much all desktops environments involved.
Migration to it can be pretty gradual and smooth, in fact you can still just keep using Xorg/TinyX/… without added issues, just bitrot starting to appear because of new hardware.
Meanwhile Systemd is pretty much one-sided and it's also an implementation that forcefully shoved itself into the ecosystem.
It broke a ton of things and still regularly breaks things.
- Wayland: protocol
- libwayland: helper library, you can choose to not use it for your own stuff (but others will likely depend on it)
- whatever compositor/display-server you're thinking about (Apache isn't HTTP)
- user applications (Google Chrome isn't HTTP either)
(And yes the wayland ecosystem has a lot of udev+linux-isms, basically because the folks that do not want udev/linux-isms didn't care about wayland for 10+ years, I was part of those btw)
- Wayland: protocol
- libwayland: helper library, you can choose to not use it for your own stuff (but others will likely depend on it)