wlroots VS wlroots-eglstreams

Even then, "tinywl" which aims to be a "minimum viable product" Wayland compositor based on wlroots is almost 1k lines:

https://github.com/swaywm/wlroots/tree/master/tinywl

>barrier has been unmaintained for a long time.

As if not having new features added for 2 years makes it stop working? barrier is perfectly fine on normal linux desktop installs. I actually use synergy 1.x personally which has been "unmaintained" for much, much longer. Except synergy 1.x will compile and run on anything from windows 98 to ubuntu 5 to debian 12. You can't get a waynergy or inputleap to compile on an OS more than 2 years old. And even then, as you say, it's crapshoot if the particular wayland will have libei; many like sway are actively hostile to it and never will: https://github.com/swaywm/wlroots/issues/2378

It looks like they actually patched it to filter those modes out, so presumably it worked out of the box and was considered undesirable: https://github.com/swaywm/wlroots/issues/3038

I haven't experienced any of those. The video game performance hit may be due to vsync, but I don't play games so I haven't noticed.

You can however use tinywl. It is an example Wayland compositor that can't do more than displaying one application.

Sway/wlroots has implemented this, but I can't find any discussion for KDE.

wlroots is archived on github. Is it abandoned? Just saying, that only means they moved git hosts :-D

A lot of compositors are based no the wlroots lirbary. So they are still sharing the development effort and have a common base, its just in the form of a library rather than a display server.

I actually got a chance to develop against some proprietary API and i don't blame them for not wanting to support proprietary drivers , But there is at least one guy maintaining a fork for nvidia so you can try your luck there.

The developer of the EGL stream fork of wlroots wants to migrate to the original version, maybe if he will become a maintainer there could be a change in the status quo, or he can maintain a fork with fixes.

Sway uses wlroots, which is one of I believe 3 wayland libraries (wlroots, smithay and taiwins). It just happens that sway (and most other compositors such as river, hikari, dwl) use wlroots, which doesn't care about nvidia. There is wlroots-eglstreams if you want to try that.

That is not entirely true, there is a fork of wlroots which supports NVIDIA's proprietary driver's EGLStreams implementation, which works fine with Sway and probably other WMs too, see https://github.com/danvd/wlroots-eglstreams.

In the meantime you can use wlroots-eglstreams

Install a fork of wlroots (the library used by Sway to do pretty much everything).

Also I know about a fork a guy did for wlroots that adds support for egl streams but this is far from ideal, it's a interesting job nonetheless https://github.com/danvd/wlroots-eglstreams

If your a technical person , you can give wlroots-eglstreams a try (it's a fork of wlroots adding nvidia support).

As of now you can run Sway with wlroots-eglstreams, which is a work-in-progress fork of wlroots, working as drop-in replacement, see https://github.com/danvd/wlroots-eglstreams and https://aur.archlinux.org/packages/wlroots-eglstreams-git/.