Gutenberg's copy of Moby Dick is 1.2MB[0]. Which is to say the slowest benchmarked terminal could display a paltry ~53 Moby Dicks per second, while shitty gives you ~98 Moby Dicks.

I am not sure how many Moby Dicks I require per second, but it is good to have options.

[0] https://www.gutenberg.org/ebooks/2701

▲

nine_k 5 hours ago | parent | next [-]

Mere 25-30 years ago I saw some very chatty Java builds run faster if the terminal window was obscured or minimized. Slow console output held back the compilers.

	▲	tdeck 5 minutes ago \| parent [-]
		In about 2013 I was an intern at Microsoft and my mentor showed me that if you were running something that streamed a lot to the terminal, it would run faster if you covered it with another window (but didn't minimize it, for some reason I don't recall). I was surprised this kind of trick was still a thing.

▲

genxy 5 hours ago | parent | prev | next [-]

Sometimes you want to dump a LOT of debug to the console but not have the console slow down that program. Or you accidentally cat a TB file?

▲

actionfromafar 5 hours ago | parent | prev [-]

Besides, most screen only show 60 images per second. That's not many Moby Dicks per second.

	▲	tosti 4 hours ago \| parent [-]
		I can't give a single FPS how much Moby Dicks per second a terminal emulator can handle!