Wayland Protocols 1.38 Brings System Bell, FIFO & Commit Timing Protocols

[phoronix]

Phoronix: Wayland Protocols 1.38 Brings System Bell, FIFO & Commit Timing Protocols

Wayland Protocols 1.38 is out with three new staging protocols...

https://www.phoronix.com/news/Wayland-Protocols-1.38

[ayumu]

For as long as I can continue to beep the pc speaker, I am happy.

[hf_139]

Banning the GNOME developer and Red Hat employee Sebastian Wick from whole freedesktop.org, and hereby also from wayland, was the absolutely right and correct decision and we see the positive consequences already.

I propose to also ban the rest of GNOME from the project. And force every Red Hat employee to mark his corporate prejudice. In example, by putting a Red Hat icon next to their name.

[Vermilion]

Cool, SDL 3 now should be Wayland-ready

[bearoso]

Banning the GNOME developer and Red Hat employee Sebastian Wick from whole freedesktop.org, and hereby also from wayland, was the absolutely right and correct decision and we see the positive consequences already.

I propose to also ban the rest of GNOME from the project. And force every Red Hat employee to mark his corporate prejudice. In example, by putting a Red Hat icon next to their name.

Jonas Ådahl works for Red Hat and facilitated this change, so they're not all like that. Some people are just jerks.

[Daktyl198]

I propose to also ban the rest of GNOME from the project. And force every Red Hat employee to mark his corporate prejudice. In example, by putting a Red Hat icon next to their name.

Nah, Wick was just exceptionally bad and abused his power too often. The proposed changes by Valve around NACKs and such will make it so that any Gnome rep can't NACK protocols just because they don't like them, while letting them participate in useful discussions in protocols they will implement. Gnome developers are still great developers with useful insight, even if they choose to go in a different direction than all other desktops and compositors.

[Errinwright]

Banning the GNOME developer and Red Hat employee Sebastian Wick from whole freedesktop.org, and hereby also from wayland, was the absolutely right and correct decision and we see the positive consequences already.

I propose to also ban the rest of GNOME from the project. And force every Red Hat employee to mark his corporate prejudice. In example, by putting a Red Hat icon next to their name.

GNOME has done more bad than good for Wayland adoption, and progression. Irrespective of them being developers in the ecosystem, their VETO rights should be rescinded in its entirety.

[MastaG]

Well some of the Gnome devs can be a pain in the ass for sure.
If you look at the whole Gnome dynamic triple buffering MR.. then this dude named "Michel Dänzer" is always critizizing everything.
I mean shit always stays unresolved for so fucking long.
Almost like they purposely don't want shit to progress.

On the other hand.. KDE 6.2 just hit Fedora and I'm now getting flickering artifacts in my screen that's connected to my Nvidia dGPU (wayland).
I guess they could be a little more strict when merging new code.

[access]

Well some of the Gnome devs can be a pain in the ass for sure.
If you look at the whole Gnome dynamic triple buffering MR.. then this dude named "Michel Dänzer" is always critizizing everything.
I mean shit always stays unresolved for so fucking long.
Almost like they purposely don't want shit to progress.

[...]

Seems like a lot of the time progress seems slow because shit is complicated (way more than one might imagine and Dunning-Kruger is in full effect for most of us on this forum) and/or waiting on stuff elsewhere in the stack. Wasn't the latest triplebuffering delay requested by the author because of some technical issues regarding the nvidia driver.

(BTW, MD is posting here occasionally)

[Daktyl198]

On the other hand.. KDE 6.2 just hit Fedora and I'm now getting flickering artifacts in my screen that's connected to my Nvidia dGPU (wayland).
I guess they could be a little more strict when merging new code.

Maybe KDE is trying to use explicit sync with nvidia but your driver is too old or something? File a bug!