green-recorder VS sway

As the developer of Green Recorder [1], the second example referred to in this page, I have to say that it sounds my abandonment statement is taken out of context.

In order to support recording on different Wayland compositors (without having to develop tons of other middle layers by yourself), one would need to simply activate their built-in screencasting tool according the specified user settings. This took me a bit of time to figure out for GNOME, and I had to fill a bug-report to speak to one of the compositor developers to understand how to do that, as no documentation was available at all. Even so, some hidden bugs appeared (Quality wasn't too good, audio had to be recorded separately over ffmpeg, and then both audio and video had to be merged together in one file, V9 had a bug that consumes 100% of CPU on some hardware, so we had to use V8 by default... etc).

In order to go further, I had to do the same thing for KWin on Wayland, Sway and other compositors out there in the market and then integrate them into my program. I had to find some workarounds for any bugs that may occur.

Later on, some changes for ffmpeg API broke the Xorg recording (Green Recorder used ffmpeg to record on all desktop environments on Xorg), so I had to do more testing now for multiple versions of ffmpeg and on which distro do they work and don't work.

So I just gave up, as I simply didn't find any particular reason to continue doing that since the only amount of support I received on my then-opened Patreon was $20 per month at its max.

But it shouldn't be said that Wayland can not support screencasting or that it breaks screencasting. It is possible, and the previously mentioned issues are actually on the compositors' developers side, not the protocol.

1: https://github.com/mhsabbagh/green-recorder

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