plotinus VS useStateMachine

This code seems to be pretty hacky, it works by injecting a dynamic library into the program and then looping on a timeout to rescan every window and attach a key handler: https://github.com/p-e-w/plotinus/blob/master/src/Keybinder....

Plotinus: A searchable command palette in every modern GTK+ application\ (10 comments)

Sublime Text is actually a good example showing that the menubar and the command palette are two unrelated things. Sublime Text implements its own command palette, which has nothing to do with the global menu on macOS. A lot of apps do the exact same thing. I don't know why people insist on tying these two features together. You can even get menubar-less GTK apps a command palette with the GTK module Plotinus, without ever having to see a menubar.

I came across this library: useStateMachine which has the closest syntax to what I was hoping to use. I’d like know what the community thinks or has any guides/suggestions.

Another option is to consider using a state machine with a library like xstate or useStateMachine. I love how state machines can simplify complex states and eliminate impossible states (ex: being in two states at the same time).

shout out to useStateMachine if you want a powerful state machine in your component

useStateMachine: A ½kb state machine hook for React\ (27 comments)

As for a comparison, I wrote about it here https://github.com/cassiozen/useStateMachine/wiki/XState-comparison

In this case, I'm using a useStateMachine hook from a library, just to avoid having to implement the not-so-relevant React part of the state handling. This hook receives the state machine we defined before as a configuration argument.