I don’t get why people cling to X so desperately. You get no benefits and downsides on top. Wayland is becoming the default for all major and even some smaller DEs, so good luck avoiding all of them and backporting features so Wayland native apps don’t break.
I’m not saying you shouldn’t do stuff like this for fun. You can do anything for fun. I don’t get why of all things you would do that for fun, but go ahead
That’s complete horseshit. There are lile 3 major implementations of Wayland and 2 exist because the other one wasn’t ready at the time. There are other hobby implementations, but they all work together. Just like how different network stacks can all talk TCP to each other and be fine. Nobody calls TCP fragmented because there are different network stacks…
There are also smaller projects.
Also, the model of a protocol allows Wayland to be deployed on truly exotic operating systems. As long as the top level is compliant, shit just works.
Lol, no. Wlroots stuff doesn’t work on Sway and vice versa, then there’s a few extra limited-scope imlementations with the same problem and Weston is reference only.
And TCP doens’t need to duplicate keyboard/mouse input and it builds on UDP to handle low-level stuff. SSH is a better example.
Lol, no. Wlroots stuff doesn’t work on Sway and vice versa, then there’s a few extra limited-scope imlementations with the same problem and Weston is reference only.
Sway is based on Wlroots. No way Wlroots stuff doesn’t work on Sway.
Ah, yup, i mixed them up. Is it 3 years already?
My point is: as it is, wayland will turn out to have one implementation (because the whole bunch of tasks it handles is complex and there’s no compositor-to-app compatibility) and everyone will require that. Or basically a X12.
Edit: nope, it was taskbars/docks that really didn’t work on both. Do they now?
Give me a compositor with at least some of the capabilities of Awesome, AND the ability to apply custom shaders to windows like picom does, and some none alpha-quality VNC solutions, then I make seriously consider a permanent move.
So it’s going to be X11 for at least 2-3 years to come for me. And this is based purely on practical and workflow reasoning. It’s is also a logical, technical, and fully informed choice, unlike the entirety of your comment.
I am running Wayland on an IVB GT1. Your hardware is not possibly shittier than this AND capable of handling modern tasks. Also wayland just needs the infrastructure of doing accelerated draws which if your GPU doesn’t support then it won’t work with X anyway unless you’re running truly exotic 2D accelerators from the 90s
I don’t get why people cling to X so desperately. You get no benefits and downsides on top. Wayland is becoming the default for all major and even some smaller DEs, so good luck avoiding all of them and backporting features so Wayland native apps don’t break.
I’m not saying you shouldn’t do stuff like this for fun. You can do anything for fun. I don’t get why of all things you would do that for fun, but go ahead
Some people see no benefit in every compositor has to reimplement everything from scratch model Wayland does.
That’s complete horseshit. There are lile 3 major implementations of Wayland and 2 exist because the other one wasn’t ready at the time. There are other hobby implementations, but they all work together. Just like how different network stacks can all talk TCP to each other and be fine. Nobody calls TCP fragmented because there are different network stacks…
There are also smaller projects.
Also, the model of a protocol allows Wayland to be deployed on truly exotic operating systems. As long as the top level is compliant, shit just works.
Lol, no. Wlroots stuff doesn’t work on Sway and vice versa, then there’s a few extra limited-scope imlementations with the same problem and Weston is reference only.
And TCP doens’t need to duplicate keyboard/mouse input and it builds on UDP to handle low-level stuff. SSH is a better example.
Sway is based on Wlroots. No way Wlroots stuff doesn’t work on Sway.
Ah, yup, i mixed them up. Is it 3 years already?
My point is: as it is, wayland will turn out to have one implementation (because the whole bunch of tasks it handles is complex and there’s no compositor-to-app compatibility) and everyone will require that. Or basically a X12.
Edit: nope, it was taskbars/docks that really didn’t work on both. Do they now?
I think there will be more collaboration regarding protocols between Gnome, KDE and Sway, but one single implementation? Hardly.
are there not just 2 main libraries or so that all the compositions implement it via?
Give me a compositor with at least some of the capabilities of Awesome, AND the ability to apply custom shaders to windows like
picomdoes, and some none alpha-quality VNC solutions, then I make seriously consider a permanent move.So it’s going to be X11 for at least 2-3 years to come for me. And this is based purely on practical and workflow reasoning. It’s is also a logical, technical, and fully informed choice, unlike the entirety of your comment.
Old computers can’t handle Wayland.
I am running Wayland on an IVB GT1. Your hardware is not possibly shittier than this AND capable of handling modern tasks. Also wayland just needs the infrastructure of doing accelerated draws which if your GPU doesn’t support then it won’t work with X anyway unless you’re running truly exotic 2D accelerators from the 90s
I installed Debian on a 2009 Toshiba netbook recently with an Intel Atom N280, KDE worked about the same (not well) in both the X and Wayland modes.
Because of resources, or because of compatibility?
My 2014 Chromebook can run sway just fine. Wayland can be lighter than x
You have no idea how old computers can be, I believe.
You have no idea how light Wayland can be.