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

[PennRobotics]

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

PR merged: "X sucks by accident."

See how easy that was, Wayland crew?

[jeoshua]

The more Valve steps up to the plate and implements sweeping fixes to long standing issues and becomes even more integral to the Linux Desktop experience, the more I start thinking that there probably needs to be an extra "/" added to Gnu/Linux.

GNU/Linux/Valve

[furtadopires]

I think that's a great idea

Basically they're gonna do the same thing they did with Proton to circumventing Wine's conservatism, which is to release out of tree features that may or may not become the official protocol implementation in the future. Kinda of "experimental protocols".

Personally I still think Khronos should be the ones handling the official Wayland protocols like they do with Vulkan (or some similar group outside Mesa), because all of this delay gives me impression that the ones responsible for that are "too busy" with other subjects to focus in test / discuss / implement new (necessary) protocols like the one Joshua specified.

[ssokolow]

I think that's a great idea

Basically they're gonna do the same thing they did with Proton to circumventing Wine's conservatism, which is to release out of tree features that may or may not become the official protocol implementation in the future. Kinda of "experimental protocols".

...and, if the divide grows big enough, you wind up with "Richard Stallman admitted he was wrong and accepted EGCS as the new GCC mainline." (The venerable GCC 2.95 being when the process was completed.) Either way, the users win.

[billyswong]

Not only that but there are more things to fix

-Global hotkey support
-Copy-paste between wayland and xwayland that doesn't break
-Drag and drop between applications is finnicky and not always working
-Window management with positions, geometry etc are lacking features.

Just to name some. Hopefully things get better faster. its been 15 years in development.
Lots of people use wayland just fine already. It depends on the needs i guess.

but for me its still a broken mess tbh.

If you don't mind XDG Desktop Portal, here is a global hotkey support that is supposed to be cross-DE https://flatpak.github.io/xdg-deskto...Shortcuts.html

There is also a window positioning Wayland protocol waiting for implementation https://gitlab.freedesktop.org/wayla...e_requests/264

[ssokolow]

If you don't mind XDG Desktop Portal, here is a global hotkey support that is supposed to be cross-DE https://flatpak.github.io/xdg-deskto...Shortcuts.html

*nod* We finally have the infrastructure in place to get non-KDE apps showing up in the unified global hotkey KCM that KDE has had since before I switched to KDE 3.x back in the early 2000s.

Likewise for the File Chooser Portal and being able to have native open/save dialogs without that crash-happy KGtk LD_PRELOAD hack. (Though KDE still needs some re-architecting to fix compatibility with the Places sidebar's "only show in this application" feature. Currently, it just sees the portal host as the application.)

[furtadopires]

...and, if the divide grows big enough, you wind up with "Richard Stallman admitted he was wrong and accepted EGCS as the new GCC mainline." Either way, the users win.

The funny thing about this situation is that, since steam is pretty much the synonym of "PC gaming" this days (specially on linux), frog protocols might not suffer from user fragmentation like the private implementations in Mutter / Kwin / Wlroots, because almost all "linux gamers" are already using Valve's software, and by consequence, are ready to use those said protocols.

[skeevy420]

...and, if the divide grows big enough, you wind up with "Richard Stallman admitted he was wrong and accepted EGCS as the new GCC mainline." (The venerable GCC 2.95 being when the process was completed.) Either way, the users win.

If the divide grows big enough it can potentially show that Wayland is being mismanaged or that they could change how their protocols work. I'm not going to pretend to know the best solution, but what I do know is that there needs to be a better way for testing experimental things and moving forward so there aren't holdups based on logical fallacies like not adding something because it hasn't been tested with enough while it can't be tested enough until it has been out in the wild to be able to come across enough setups to catch oddball bugs and issues and then work things out before finalizing them as official Wayland protocols.

[Errinwright]

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.

The GNOME foundation behaves like a tumour that is metastasizing at an accelerated rate. At this point we need a quarantine zone large enough to seal them off from the rest of the ecosystem.

[bkdwt]

This is the difference when you have paid people doing the things.