> Please take into consideration that Casey's definition of the solution as "simple" can sound quite insulting as well.
It can sound insulting only to people who originally claimed that what Casey suggested requires "doctoral level research into performance". Only to then implement exactly what he suggested.
> If someone stated that something is "simple" with an overtone of "are you blind", instead of showing more humility
He is there trying to understand an issue, providing suggestions etc. And generally being baffled how a modern terminal on a modern machine can output text at something like 5 frames per second.
After that Windows Terminal team barges in with "what you’re doing is describing something that might be considered an entire doctoral research project in performant terminal emulation" to... only do exactly that later.
It can sound insulting only to people who originally claimed that what Casey suggested requires "doctoral level research into performance". Only to then implement exactly what he suggested.
> If someone stated that something is "simple" with an overtone of "are you blind", instead of showing more humility
Please re-read the original GitHub issue from the start: https://github.com/microsoft/terminal/issues/10362
He is there trying to understand an issue, providing suggestions etc. And generally being baffled how a modern terminal on a modern machine can output text at something like 5 frames per second.
After that Windows Terminal team barges in with "what you’re doing is describing something that might be considered an entire doctoral research project in performant terminal emulation" to... only do exactly that later.
And what Casey said was going to be simple is this: https://github.com/microsoft/terminal/issues/10362#issuecomm...
Tell me how this is insulting to anyone except the people who now claim that "oh we'd been aware about this approach before Casey opened the issue"?