Quantity != quality.
Especially when the majority of those users are likely not using it by choice.
Casey submitted a bug saying that it’s slow and should be much much faster.
Microsoft responded something like “text is hard … … phd dissertation on rendering text”
Casey made a terminal renderer with more features than Microsoft’s renderer in a weekend, it performed orders of magnitude faster, had zero optimization work performed and he jokingly (and hilariously) titled the video “a phd dissertation”.
Next, the excuse parade rolled in and came up with all manner of excuses as to why Muratoris renderer was so much faster, so he made a follow up video addressing the excuse parade, as well as containing some very minor optimization.
Also note that Casey’s implementation isn’t even as fast as things could be. His optimizations are minor.
https://github.com/microsoft/terminal/issues/10362
https://m.youtube.com/playlist?list=PLEMXAbCVnmY6zCgpCFlgggR...
https://github.com/microsoft/terminal/issues/10362
It's nothing serious just microsoft engineers writing slow as shit code and reacting poorly to someone trying to help.
Always they had a reputation of being slimy with low quality code, bugs.
Of course the whole Casey Muratori incident also made it clear how terrible Microsoft programmers are.
I worked with 2 Microsoft principal engineers in my life and I swore I would never work with another Microsoft dev since then.