Wayland's Weston 12.0 Released With Multi-GPU Support, PipeWire Backend, Tearing Control

[phoronix]

Phoronix: Wayland's Weston 12.0 Released With Multi-GPU Support, PipeWire Backend, Tearing Control

Weston 12.0 as Wayland's reference compositor is now available with multiple GPU support in the DRM back-end, support for HDMI content types, support for the Wayland tearing control protocol, plane alpha DRM property handling, a PipeWire back-end, and much more...

https://www.phoronix.com/news/Wayland-Weston-12.0

[MorrisS.]

What is the reason KDe PLASMA doesn't adopt weston?

[ssokolow]

What is the reason KDe PLASMA doesn't adopt weston?

Not from KDE, but the most logical assumption is that they decided it'd be more work to port KWin's giant pile of features, compositor effects plugin API included, to Weston than to port KWin to Wayland.

[V1tol]

What is the reason KDe PLASMA doesn't adopt weston?

That's a quite hard question to answer similar to "why develop Linux, we have Windows". How I would answer if I was a KDE developer.

• Quite big amount of time needed to learn a new library even before starting to integrate it
• Integration may be impossible due to architecture differences, or lead to huge amount of badly maintanable glue code
• GNOME does not depend on Weston
• I am a proud developer and don't want to throw away code I wrote and know well in favor of something unknown

[Quackdoc]

What is the reason KDe PLASMA doesn't adopt weston?

What is the reason Gnome doesn't adopt kwin? or any of them adopt wlroots, or weston adopt mutter? because doing things your way is often better and easier then trying to force a different tool to work for you

[oiaohm]

What is the reason Gnome doesn't adopt kwin? or any of them adopt wlroots, or weston adopt mutter? because doing things your way is often better and easier then trying to force a different tool to work for you

Gnome and kde start porting their compositor to Wayland before wlroots/sway exists.

Also pays to be aware for quite some time mutter depending on Xwayland to function. Why because mutter was for a long time using lots of legacy X11 compositor code basically as is with Wayland applications.

https://www.phoronix.com/news/KDE-XWaylandVideoBridge

Yes mutter had something like this XWaylandVideoBrigde internally for quite some time so the old X11 compositor/windows manager code would work as is.

What mutter did in the past does bring interesting point. If you are willing to put up with overhead and someone is willing to put in the time X11 windows managers could be make work with a Wayland compositor.

[mos87]

Deadware.
Pray it's not THE future of free GUI.

[Zapp!]

Deadware.
Pray it's not THE future of free GUI.

Since Weston is used for WSL2 GUI apps it's far from dead - it's probably the most widely used Wayland compositor.
Why Microsoft chose Weston is beyond me, though.

[Sonadow]

Since Weston is used for WSL2 GUI apps it's far from dead - it's probably the most widely used Wayland compositor.
Why Microsoft chose Weston is beyond me, though.

Because it's the most simple, barebones compositor available.

You are running Linux GUI software on Windows, not running a full desktop environment and window manager.

[Quackdoc]

Deadware.
Pray it's not THE future of free GUI.

how does one even arrive to this conclusion? weston is the official compositor of AGL, well libweston. I would say that due to this alone, weston is probably the most used compositor of all of wayland compositors. let alone WSL2, I know it's used in industrial uses, set top boxes etc.