Open koekeishiya opened 1 year ago
There will not be feature parity, so replace is probably the wrong word. But this is what I will be using personally in the future.
What does this mean? What will meraki make better? (Can't wait for it 👍 )
Current reference for the implementation: https://github.com/koekeishiya/meraki/blob/master/examples/merakirc
😻With the ability to make keybindings for specific apps only, this will be an excellent replacement for karabiner
This project will take a different direction altogether. Forget everything that has been said about this so far. This will go back to early kwm days if anyone still remembers, when hotkeys were defined in a hotloadable C module.
The motivation is to get rid of unnecessary delay for certain operations, by allowing hotkeys to run functionality written directly in C. This will not be very different in practice from software that exposes Lua / JS environments in which the user supplies scripts/snippets that the core software executes through various hooks.
e.g. interfacing with yabai from such a system will remove the fork-exec overhead completely, which amounts to roughly 50% of time spent for most command invocation in todays skhd -> yabai pipeline.
I get the impression that people might be intimidated by C, compared to Lua/JS /\
Is this used to replace skhd?