Thread with 4 posts
jump to expanded post
,
@wez@fosstodon.org
@zlatko FWIW, wezterm throttles the `time cat bigfile` case in order to remain responsive to interrupts, so this comparison is not as meaningful as folks think it is.
@wez uh, good catch. I saw people on lobsters commenting about that, so I wondered and checked.
On the one hand, I wonder what would be a meaningful test, though? Pressing ctrl-c sequence and seeing how many lines past through before the interrupt caught? Repeat many times to average it out?
On the other hand, I don't think it matters in most of the day-to-day work. I can't read that fast. The times things scroll that fast, I want both: a way to interrupt immediately, as well as the whole sequence going through very fast.
@wez
This comment about the interrupt remained me.
I wonder if you saw the article on the new major release of fish shell and their point about parallelism. Like, they can't do many things in parallel with C++ because they keep shooting themselves in their feet, so they switched to rust. I wonder if that kind of parallelism is used in catching interrupts (and regular user input) vs rendering.
Lots to think about.