|
|
|
|
|
|
by tazu
651 days ago
|
|
|
This is why Textualize[1] concerns me. I've tried a few of the applications using their framework, and they have noticable keypress latency. I didn't think it was possible to make a bloated TUI, but they have somehow succeeded. This might just be a Python thing because of the GIL, because VisiData[2] has the same problem. It's physically jarring to use VisiData because it's such a cool idea, but takes 500ms to register key presses in my 120hz terminal emulator. It's reminiscent of scroll-jacking, excessive animation, and other web GUI bloat, just translated to TUIs. [1]: https://www.textualize.io/ [2]: https://www.visidata.org/ |
|
|
I don't know what the issue is on your computer, but it definitely doesn't take my computer 500ms to register a key press in VisiData in the general case. That would be an issue I'd have to take seriously. I've spent way too much time optimizing VisiData's startup time to be under 300ms to let something like that slide. It's a point of pride for me that VisiData doesn't incorporate that "web GUI bloat" as you mention.
If you're willing to help out, please contact me so we can file an informative issue and see if we can figure out what's going on in your setup. I have a hunch it's generalized computer/OS bloat that we (VisiData) can't do anything about, but at least we can try to understand it so that hand-crafted software like VisiData isn't unnecessarily maligned.