Question about the future of Xorg

[Vasily]

> 
> that's not a wayland thing. wayland is just a protocol plus associated
> tooling and libraries to speak that protocol. panning is a compositor thing.
> 
> if you wanted a compositor to support this then add it to that compositor. as
> there is no single compositor in the wayland universe, you'd have to make a
> choice. you could also build your own compositor.
> 

And that is the main issue with wayland.
"Very intelligent" people created a protocol plus associated tooling and libraries and expected that community will build a new great compositor.
But if X11 was developed for ages and polished for decades by people who loved it, no one want to spend his time and design a new compositor for every 
existing GPU
Because in this case it will be just another X11.

If you take a look on Linux there are few servers in it already - like systemd or dbus, pulse/pipewire, named ...
For my understanding there is nothing wrong with a server/client approach and right now there is not any evidence that there is a wayland compositor 
that works like X11
Second problem that desktop must adopt such compositor.

My personal opinion is that there are some issues need to be solved before wayland compositor can substitute X11.
So I think X11 will work for us another 5 -10 years.