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?
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?