I'm in the process of replacing low-level Windows code with keytap and so far, it seems to be working great!
However, I would like to ask whether you are open to replacing the crossbeam channels with their std counterparts.
Background: the keyboard listening code of my own project was originally copied from Espanso where they used crossbeam as well. But the functionality I needed is (nowadays) also offered by the standard library. Therefore, to minimize the number and size of my dependencies, I refactored my code accordingly. It made my release binary about 40 KiB smaller.
But now that I'm adding keytap, I get back that crossbeam dependency. 😢
Of course that may simply be a "me" problem that you are perfectly entitled to not care about. Still, I wanted to at least propose the change.
I'm in the process of replacing low-level Windows code with
keytapand so far, it seems to be working great!However, I would like to ask whether you are open to replacing the
crossbeamchannels with theirstdcounterparts.Background: the keyboard listening code of my own project was originally copied from Espanso where they used
crossbeamas well. But the functionality I needed is (nowadays) also offered by the standard library. Therefore, to minimize the number and size of my dependencies, I refactored my code accordingly. It made my release binary about 40 KiB smaller.But now that I'm adding keytap, I get back that
crossbeamdependency. 😢Of course that may simply be a "me" problem that you are perfectly entitled to not care about. Still, I wanted to at least propose the change.