wlroots-eglstreams VS sway

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/.

This is partially why i use tools like i3 (/ sway). i like the tool; it works extremely well for me; the design has stayed the same for 20 years; there's no profit motive to come along and fuck everything up. it just works. it is boring in the best way possible.

I also have crashes on sway, but there’s a rough workaround now which prevents the issue totally.

I believe there’s a design issue with Firefox and GTK handling input events; some Wayland compositors have workarounds but others do not.

https://github.com/swaywm/sway/issues/7645

https://bugzilla.mozilla.org/show_bug.cgi?id=1743144

Firefox is my preferred browser and I hope we can keep its engine alive in this era of Chrome dominance.

I'm seeing this: https://github.com/swaywm/sway/wiki/Setting-Environmental-Variables but I haven't figured out how to make GDM do it, and I was wondering if there was a super simple "HEY SWAY READ MY .PROFILE" thing I could do.

So I searched around and found the following bug report where this problem and a possible solution was borough up: https://github.com/swaywm/sway/issues/2966 , which was then immediately closed again.

I've been using Sway since late 2019. I like the workflow of a WM. I honestly find it hard to go back to a DE, I like having a minimalistic desktop.

Sway is fast, minimal, and flexible. Their recommended tools/addons are worth a look: https://github.com/swaywm/sway/wiki/Useful-add-ons-for-sway

From that list I use greetd + tuigreet as my login manager, sway-launcher-desktop for FZF-powered app launching, and wob for lightweight brightness and volume display (send '50' to the wob socket and it'll show 50%; it doesn't get simpler).