Comment by phtrivier

Oh, sorry if that's the tone that got out of my message. I'm a big Casey fan myself, so I'm absolutely convinced that there is something "better" to do in terms of performance.

However, just because Windows Terminal was "new" in 2019, it does not mean that it was not embarking lots of legacy code to ensure compatibility with older software.

For example, the wikipedia page you linked to explicitly says WinTerm is "a replacement for Windows Console", which dates back to Win 9x [1] ; and that it's "compatible with Windows Narrator" [2], which dates from the early 2000s, and which scares me just by its name...

So, yes, there is probably a story of piling crap on top of backward compatible crap with zero incentive for performance, and an unhealthy dose a learned-helplessness.

I don't necessarily says it's an excuse for the problem ; but I would really not be surprised if it was "part" of the problem that MS is facing, and that Casey attacked a slightly different problem by not caring about obscure retro-compatibility to Win3.1.

It's good that the team used the software to improve their own. They're in a better position to argue than armchair commentators like me.

[1] https://en.wikipedia.org/wiki/Windows_Console#Windows_9x

[2] https://en.wikipedia.org/wiki/Narrator_(Windows)