The best plot twist in this particular excuse parade is the excusemaker later saying that the hard problem to solve is if you "cat the wrong file or get a ridiculous output from a tool". Which is exactly what I demoed being very fast in refterm!https://twitter.com/roytries/status/1412457848676757505 …
-
-
Yeah, I don't know.. Maybe he thought you *only* solved high framerate terminal rendering, but you clearly did way more, and even showed off the fast pipes demonstrating that Windows is way too slow here. I hope he'll get round to watching the entire video some day..

-
Well the reason this stuff pisses me off is because actually, _I didn't do way more_. The code I showed was unoptimized! What I was trying to show was not that I could write an amazing terminal, it was to show that _the laziest terminal code is 7000fps and cats huge files fast_.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
I'm just trying to understand how Roy came to say the things he said.. I think he wanted to say that a poorly optimized terminal window would be perfectly usable if it flushed stdout as fast as Casey's refterm.