However, the sole reason I'm keeping an eye out for raycast-compatible launchers is the ability to integrate the raindrop.io extension - which seems to be broken when used through Vicinae.
Maybe someone else running raindrop got it to work; "TypeError: Cannot read properties of undefined (reading 'subscribers')".
Mostly comparison of consumed RAM with identical set of extensions might help me choose without trying each of this projects.
Or after a while without interaction bloated RAM get swapped out and launcher invocation need to fetch swapped out info.
For comparison here is how krunner looks on my current machine. After some time without interactions:
$ systemctl --user status plasma-krunner.service|head
● plasma-krunner.service - KRunner
Loaded: loaded (/usr/lib/systemd/user/plasma-krunner.service; static)
Active: active (running) since Sun 2025-08-10 20:31:40 WEST; 1 month 12 days ago
Main PID: 57749 (krunner)
Tasks: 37 (limit: 17782)
Memory: 64.6M (peak: 1.4G swap: 338.2M swap peak: 679.8M zswap: 12.4M)
CPU: 2h 58.702s
CGroup: /user.slice/user-1000.slice/user@1000.service/background.slice/plasma-krunner.service
└─57749 /usr/bin/krunner
It seems to me I feel how it was less on the first invocation.Great to see it already has a Nix flake too! I was able to get it setup basically instantly.
I'm used to drun/rofi and enjoy their simplicity, but have also secretly envied the out-of-the-box experience of more fully featured launchers on macOS. I remember using Spotlight and Alfred many years ago, and being impressed by the experience.
I like that you chose to make it compatible with Raycast, and how easy it is to extend, based on a quick look at the docs.
I'll definitely keep an eye on your project, and give it a try. Thanks for sharing!