That already happens constantly and I’d consider this the consequence of it, rather than the cause. You can only issue so many vetoes before people no longer want to deal with you and would rather move on.
The recent week of Wayland news (including the proposal from a few hours ago to restate NACK policies) is starting to feel like the final attempt to right things before a hard fork of Wayland. I’ve been following wayland-protocols/devel/etc from the outside for a year or two and the vibes have been trending that way for a while.
No one will use a fork of Wayland. That would be suicide. The Wayland project will continue no matter what other things people are working on. I can see a separate project forming but it strongly doubt it will have any traction.
If you recall back to the days of the yearly internet people said the same thing about TCP/IP
The problem is that you could end up with protocols that certain desktops don’t want to implement.
That already happens constantly and I’d consider this the consequence of it, rather than the cause. You can only issue so many vetoes before people no longer want to deal with you and would rather move on.
The recent week of Wayland news (including the proposal from a few hours ago to restate NACK policies) is starting to feel like the final attempt to right things before a hard fork of Wayland. I’ve been following wayland-protocols/devel/etc from the outside for a year or two and the vibes have been trending that way for a while.
No one will use a fork of Wayland. That would be suicide. The Wayland project will continue no matter what other things people are working on. I can see a separate project forming but it strongly doubt it will have any traction.
If you recall back to the days of the yearly internet people said the same thing about TCP/IP
Famous last words …