[GrinningFool]

This is really cool and it's clear that a lot of work went into it. I've used it a bit and it's generally solid.

I've been looking for improved terminal clients for years. To that end, I have a simple benchmark that I run:

    find / 

Then repeat the same within a tmux session. In both cases I check to see if I can interrupt the output with Ctrl+C.

Hyper on linux under X actually stops rendering the output very quickly, but all subsequent input is ignored. The tmux case was the same. In addition, CPU usage spiked to 2 procs each @ 100%. Interrupting the shell was not possible with Ctrl+C or other means, though I was able to `SIGKILL` it.

This particular test is my personal benchmark of whether I can use a terminal - because nothing is more frustrating than having to kill an entire session because of a typo or bad command that generates a lot of output. Too, clients that struggle with this also have a tendency to slowly render changing curses layouts on large terminals - such as when resizing tmux panes, or rendering large amounts of scrolling content in a sub-region of the terminal.

This is a simple case, and many native clients struggle with it as well. So far, although it's not my most-favorite to use, `konsole` is the only one that handles this well.

[kLeeIsDead]

Heh... Javascript.

[stcredzero]

To that end, I have a simple benchmark that I run:

    find / 

Well crap. Years ago during an phone interview for a position that wasn't going to use Python, I was discussing that the current python script was exponential, then I wondered what would happen if I just let it run. It very quickly completely froze my laptop. In VisualWorks Smalltalk, I would have been able to Ctrl-Y interrupt into the "emergency evaluator." Python has nothing like an "emergency evaluator." How uncivilized of it! Interpretation of my interviewer: I am a stupid fake programmer person who doesn't understand exponential time/space complexity. [sigh] -- No I just don't understand why someone would build a tool like that! I guess I was spoiled.

[qwertyuiop924]

And C-c didn't work? You must have let it run a really long time. I'm surprised it didn't error out.

[stcredzero]

You must have let it run a really long time.

All of about 5 seconds.

[GrinningFool]

Clearly you should not have run that script at all - it was a trick.