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.
Sway is based on Wlroots. No way Wlroots stuff doesn’t work on Sway.
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.
deleted by creator
Sway is based on Wlroots. No way Wlroots stuff doesn’t work on Sway.
deleted by creator
deleted by creator
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?