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 …
-
-
I’m late to the party, but why should terminal rendering slow down performance of the process outputting to stdout? Shouldn’t it just generate a correct rendering 60 times per second, each one reflecting the state of the output 1/60th of a second ago?
-
The problem seems to be a difference in performance expectations between game developers and... well, everyone else.
End of conversation
New conversation -
-
-
Would the same principles you demonstrated with refterm also apply to say, a debugger? Because catting large files at the cmd prompt is not a typical task for me, but dumping gigabytes of memory with windbg and then growing old waiting for the output is a *daily* nuisance for me
-
I'm not familiar with windbg dumps really, so I can't speculate on whether / why they might be slow.
End of conversation
New conversation -
-
-
Next issue - your manners:https://twitter.com/roytries/status/1412482789287604230?s=20 …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Oh Roy. Misreads the vibe, comes to the party with a half baked potato, then accuses you of "inconsiderate behaviour". Anyone got a mirror around here?
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.