Arijit Basu

I'll probably need to get a test suit up to measure the cpu usage in a vm environment.

Initial flamegraph:  CPU usage: 51% Conclusion: We are reading the keyboard inputs wrong.

Try 1: https://github.com/sayanarijit/xplr/pull/26/commits/1bfb01140d8cf3e5933b41da01e2fbdf3a5ff133 Flamegraph:  CPU usage: 17% (for other reasons) Conclusion: Reading keys in a blocking way partly fixes the load issue, but we get error when we invoke...

I'll continue working on it after https://github.com/sayanarijit/xplr/issues/39 to make sure we don't break anything in order to optimize things.

Related: https://github.com/crossterm-rs/crossterm/issues/397

The [suggested solution](https://github.com/crossterm-rs/crossterm/issues/560) was to rewrite the codebase in `async` rust which I don't think is a good idea for this project as of now since we're still in the...

It doesn't seem to have much impact in my machine since the sleep time should apply only for the first click. When holding the key, subsequent events should be faster.

Awesome. Thanks.

It will definitely get better as `xplr` stabilizes.

Just to keep everyone in the know, a lot of CPU and performance optimizations were made. The latest version uses about 0.1% - 0.7% CPU when idle and also feels...