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 …
-
-
As I'll show next weekend, I _did_ then go and add literally like 20 lines of optimization to refterm after that demo. And guess what? IT GOT ANOTHER 10x FASTER. So like, I just don't even anymore. I just don't even. I should have been a mason like my grandfather.
-
"I mean, sure, you built a wall that can hold the specified weight in less than two days but the REAL problem is the buttressing. This demo doesn't even address the issue of mortar which is this primary obstacle facing business masons."
End of conversation
New conversation -
-
-
Would you be ok with someone making a 10s video compilation of all of refterm's features and speed? Could filter out lots of low-effort dismissals
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.