Frog-FIFO-V1 Aims To Address Mesa's "Fundamentally Broken" Wayland Code

[NekkoDroid]

Wlroots has been doing this for ages, they have their own batch of wlr-* protocols for use today on sway (and often picked up by other compositors) while they're getting upstreamed into wayland proper:

https://gitlab.freedesktop.org/wlroots/wlr-protocols/-/tree/master/unstable?ref_type=heads

The eagle-eyed will recognise many of these as already upstreamed into wayland.

Do note that wlr-protocols doesn't really accept new protocols and instead they should be proposed upstream at wayland-protocols. But almost all compositors have their own private protocols (I know atleast GNOME and KDE have) which they upstream when it makes sense.

[avis]

Any Valve employees here?

Could you guys consider this as a next step?

https://gitlab.freedesktop.org/wayland/wayland/-/issues/233

[fahrenheit]

X being a mess is no excuse to sabotage people trying to use it's replacement.

The Steam Deck is arguably the most popular commercial PC that ships with Wayland right now.

Actually that would be ChromeOS. And in the ChromeOS case Google (like Valve) are also fans of shipping working stuff now instead of waiting for upstream (not just wayland, but mesa, kernel, etc).

[theriddick]

on todays edition of wayland is a broken by design clusterfuck that still isnt fixed 15 years later:

HOW DARE YOU INSULT WAYLAND! REEEEEEEEEEEEEEEEEEEEEEEE

[fitzie]

i love how all the reasons not to allow this improvement in is entirely non technical "oh noes the quality will suffer" we need "community input". all this code is open source they can fix the protocols any time they want, they can even get rid of broken protocols. they were able to do this without any issues in X11 but for some reason they seem to think it's some sort of inevitable outcome if they don't sit on things for years and years. I wish some of the old x11 devs like keithp were still involved. He'd get this sorted out really quickly. imagine if the wayland cabal actually worked on a roadmap to deliver features instead of talking about them forever? Imagine if cross compositor compatibility was a desired goal and they had leaders that would pull together the compositors instead of them doing their own thing because they want to reinvent the desktop in their own clever way?

i'm sure it'll be fixed now for sure, that in 2025 there will not be any reason left to use x11. honestly, I wish the companies behind desktop graphics for linux would just pull in linux foundation to figure out how to put serious people back in charge of linux graphics.

[royce]

Do note that wlr-protocols doesn't really accept new protocols and instead they should be proposed upstream at wayland-protocols. But almost all compositors have their own private protocols (I know atleast GNOME and KDE have) which they upstream when it makes sense.

This is true, I imagine since Simon Ser got heavily involved upstream there wasn't any need for it anymore. But still, my point stands. It's worked out well.

[gotar]

i love how all the reasons not to allow this improvement in is entirely non technical "oh noes the quality will suffer" we need "community input".

This is simply the GNOME fandom sabotaging competing DMs/WMs.
And they force Their Newer Better UI standards just like any typical control freaks.

But what could anyone expect from guys failing miserably at X11 development? Scrubs stay scrubs, even after project change.
We have a saying: if a brothel makes losses, change the hookers not the curtains.

[jeisom]

Hopefully frog-protocols will trigger a speed up of wayland-protocols on top of getting this all in the hands of users sooner.

[ssokolow]

To recap: X sucks ass on accident. Wayland sucks ass on purpose.

If you're gonna phrase it "on accident", you might as well be fully wrong and also use "by purpose".

[Britoid]

Actually that would be ChromeOS. And in the ChromeOS case Google (like Valve) are also fans of shipping working stuff now instead of waiting for upstream (not just wayland, but mesa, kernel, etc).

Unless it's changed, I last remember that ChromeOS uses its own protocol but supports a Wayland compatible proxy.