gabm

interesting, thats indeed a bug and shouldn't happen...

I agree.. but i don't have a 100% good idea on how to keep the interface lean with the increasing number of options/settings

there are some ideas in #42 and #49

I think you are right with this. That would be great! The technical foundation is there but my time is limited atm.. I can provide guidance though

great, i can help to give you a headstart.. you can contact me on matrix: @gabm:matrix.org. The tech stack is: - rust as programming language - gtk/relm as UI Framework...

I am not against it. But I am not sure, if we have the time to develop and maintain those features?

do you use the ppm image format? that should be faster (see README). Apart from that, we might need to run the initial image reading from stdin in async .....

ppm is faster for loading, because it's uncompressed. png is using zip inside which is single threaded and may run a tiny bit slower. As output format we only support...

I did some benchmarks w.r.t. intra-app startup and there the major factor was png decoding. You claim that most of the startup time is loading of libadwaita. Might be. Can...

yes you do but I'm not sure that this is bottleneck... i also feel that satty could start up faster, but I'm not sure what is "slow". We need to...