It’s not as much of rewriting Xorg cleanly but also rethinking how we handle graphical sessions as a whole, accounting for how tech works and where it’s going.
It does lead to things like not being able to put your window at position (x,y) because what if you’re in VR and now your window position is some 3x3 matrix. But that’s a good thing, we’re thinking of those use cases instead of writing something that will need breaking changes later. Wayland likes to make no assumptions, so you can use it on phones or even do some rather exotic stuff. You could implement a Wayland compositor that outputs a video stream instead of on a real screen if you want to. You can make a true multi-user compositor with multiple mouse and keyboards that’s not horribly broken like it is on Xorg. You can make a distributed Wayland compositor that runs across multiple machines. You can make a compositor optimized for e-ink displays. It makes no assumptions that a computer always have a monitor, keyboard and mouse, or what kind.
We could just write something that works and that wouldn’t have any of the typical Wayland complaints. But it doesn’t solve things like VR, phones, tablets, TVs, etc, it would only re-solve Xorg and displaying windows and titlebars and panels.
That’s why we’re not writing a display server, but instead a series of protocols that anyone can implement and handle however the hell they want. We can have specialized compositors rather than one giant display server that needs to implement every possible use case. We’re still not quite at feature parity on the desktop yet, but that’s just not the sole end goal of Wayland in the first place.
IMHO with 5+G and symmetric 1G+ speeds becoming generic soon, it seems “network is the computer” minus Ellison’s evil intentions happening.
Even today, most people can’t or won’t own a top end GPU with a decent amount of memory. Ok you can afford it but it will be outdated in 6 months. I would get a service instead so I really wouldn’t care about pixels per second.
I am telling these as a person who uses Wayland for a very long time even on GPUs including nv9400, thanks to Nouveau. So I don’t have anything against Wayland but same time, I am using X remote functionality every single day to do things.
The colour correcting capabilities are just getting stable, developers are systemd like arrogant and disconnected from real life.
Xorg needs several of it’s extensions to function at the same level as Weston+Wayland. At minimum you’d need xorg server, proto, lib, and driver… Maybe a few other things I’m forgetting.
Isn’t the main Argument that it has a smaller, cleaner and more modern codebase, which is easier to maintain. And has a smaller attack surface?
It’s not as much of rewriting Xorg cleanly but also rethinking how we handle graphical sessions as a whole, accounting for how tech works and where it’s going.
It does lead to things like not being able to put your window at position (x,y) because what if you’re in VR and now your window position is some 3x3 matrix. But that’s a good thing, we’re thinking of those use cases instead of writing something that will need breaking changes later. Wayland likes to make no assumptions, so you can use it on phones or even do some rather exotic stuff. You could implement a Wayland compositor that outputs a video stream instead of on a real screen if you want to. You can make a true multi-user compositor with multiple mouse and keyboards that’s not horribly broken like it is on Xorg. You can make a distributed Wayland compositor that runs across multiple machines. You can make a compositor optimized for e-ink displays. It makes no assumptions that a computer always have a monitor, keyboard and mouse, or what kind.
We could just write something that works and that wouldn’t have any of the typical Wayland complaints. But it doesn’t solve things like VR, phones, tablets, TVs, etc, it would only re-solve Xorg and displaying windows and titlebars and panels.
That’s why we’re not writing a display server, but instead a series of protocols that anyone can implement and handle however the hell they want. We can have specialized compositors rather than one giant display server that needs to implement every possible use case. We’re still not quite at feature parity on the desktop yet, but that’s just not the sole end goal of Wayland in the first place.
IMHO with 5+G and symmetric 1G+ speeds becoming generic soon, it seems “network is the computer” minus Ellison’s evil intentions happening.
Even today, most people can’t or won’t own a top end GPU with a decent amount of memory. Ok you can afford it but it will be outdated in 6 months. I would get a service instead so I really wouldn’t care about pixels per second.
I am telling these as a person who uses Wayland for a very long time even on GPUs including nv9400, thanks to Nouveau. So I don’t have anything against Wayland but same time, I am using X remote functionality every single day to do things.
The colour correcting capabilities are just getting stable, developers are systemd like arrogant and disconnected from real life.
Depends on the implementation. The reference, Weston, is not.
Weston is by file size, about equal to xserver. But really there is more utility in Weston than xserver.
But it’s one monolith, same as X.
Xorg needs several of it’s extensions to function at the same level as Weston+Wayland. At minimum you’d need xorg server, proto, lib, and driver… Maybe a few other things I’m forgetting.