A quick shallow look.

• Avoid single hard paths. Provide fall-backs. Make them all configurable. Use xdg (properly)...etc.
• Avoid .unwrap() or any source of panic!() for non-fatal things that can actually fail.
• Make non strictly necessary fields optional in you model, if that helps.
• Use .filter_map() and .collect() in your parsing code, instead of all the matches and continues in a for loop. You can use .ok()? to early-return with None on errors.
• And finally, since you're micro-benchmarking, try speedy or borsh instead of bincode, unless you need the serde compat for some reason.

Unfortunately, there's already popular software called ‘flux’, or rather ‘f.lux’: the one that turns the screen redder in the evening to mirror the natural light. It's the app that did it first, predating this function in the OSes, and still doing it better than most ‘native’ implementations.

Gave it a whirl, on Arch with wayland, but I kept getting a panic error.

Nice project, I really like the minimal design!

I also experienced a panic on image load.

My rule of thumb for error handling: try to avoid unwrap. Use expect with a nice error message. And only use expect for stuff that should never fail. And bubbling up the errors to the top with ? is also useful.

Guys, do you have any ideas for a name?

Yes I need this! Krunner is so slow.

How does this compare to anyrun?