DMA-BUF being marked as "unstable" for a decade was a fucking joke. It's a protocol that's required to get any kind of meaningful hardware accel going, which nearly every app does nowadays. Within Wayland circles, it's been understood it's not going to change for years, as doing so would break nearly every single existing app, yet all kinds of bikeshedding prevented it from being moved to stable.

Hopefully this marks a turning point for many other similarly important protocols stuck in unstable/staging hell too, like pointer constraints and text input. If devs can't rely on basic functionality to be present and it takes more than say three years to commit to it, it's time to admit that either the process or the protocol is broken.

Sounds cool

This is the best summary I could come up with:

With Wayland Protocols 1.33 there are various fixes/clarifications and then two main changes: Linux DMA-BUF is now considered stable and the transient seat protocol (ext-transient-seat) is introduced for the first time.

The Linux DMA-BUF protocol for Wayland is widely used these days and supported by multiple compositors for negotiating optimal buffer allocation parameters between clients and compositors.

The current fifth version of linux-dmabuf was marked as stable with it working out well and no need for any other changes before removing the "experimental" tag.

These transient seats will be automatically removed as soon as the client disconnects.

The transient seat protocol is intended for use with Wayland's virtual input and virtual pointer protocols for remote desktop use.

Wayland's transient seat protocol already has support for Sway / wlroots along with WayVNC.

The original article contains 226 words, the summary contains 131 words. Saved 42%. I'm a bot and I'm open source!