rofi-org-todo VS wlroots

(note and disclosure: I use a rofi compatible wayland package... and have actually written a rofi plugin to keep me in flow https://github.com/wakatara/rofi-org-todo )

I leave the todos in the daily files (in org super-agenda it gives them context) and then generally have org-roam links if they are related to a project and the person and then use tags like :perso: or :work: and usually a week if they are not scheduled (eg. :w49:), so they are separable in the agenda. This helps me focus on things that are important (also, you can tab to collapse or expand section using origami in super-agenda which helps to focus or not. I do have an inbox.org file for capture (and one called inbox13.org for my mobile device separately since I've had conflicts on Dropbox and iCloud before) though this is more to get stuff out of my head quickly (I'm the author of rofi-org-todo https://github.com/wakatara/rofi-org-todo ) and then I just process the inbox a la Dave Allen and usually put them with context notes in the daily file.

I use an Alfred (I'm on OSX) TODO capture which throws things into an inbox since I find that more comfy than in-emacs capture. If you are in Linux and use the (amazing) rofi, I also wrote a rofi mode to do the same thing for i3 and sway. Ubiquitous capture is definitely the way to go (and please read David Allen's Getting Things Done for more on that... =] ).

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.