I read through the Windows Terminal Github a lot, and have for a long time. It's a really interesting project to follow. I saw all these threads play out in real time. No, the Microsoft team was not perfect, back then or now, but it's not the witch hunt it's being made out to be here. DHowett, lhecker, zadjii, and probably some I'm forgetting readily admitted that multiple times on multiple Github threads with Dhowett even saying a literal "sorry" to Casey in name while accrediting the in progress work to his suggestions as early as November of last year despite the countless comments here about the blog posts in 2022 not being proper enough apologies because of the lack of these things. I also don't blame any of these folks for not wanting to link back to the GitHub comments of what amounts to flame wars on issues, some closed and some still open as they do actually care about making the performance better for more use cases, and instead leave them to be focused on the technical aspects now that they are finally steered in that position.
It's also worth noting there was a non-Microsoft individual out of China cmuratori et al had a lot of early communication issues with. They also apologized individually and ended up dropping out of contributing to the project (mostly performance related commits) last year due to some of the things said about them on GitHub and Twitter.
Imperfectness of the terminal committers aside, past and current, I don't think I've ever seen something approaching an apology for anything from cmuratori (though admittedly I don't follow anything outside Github as I'm just trying to follow the changes). I have seen the guy go out of his way to write an alternative demo terminal (licensed in a way the Microsoft folks can't even read it on GitHub if they wanted to) rather than actually try to help the project... and have folks like lhecker kindly responding to GitHub comments about it while he was working on making it happen in the real Windows Terminal codebase.
For all that still just want to gang up on the Windows Terminal team here because they can find something they did that wasn't perfect I'd just say they've handled it better than I think 95% of HN would have, better than I would have for sure, and you shouldn't give this troll more of a platform even if he was right about the technical approach in this case (though wrong about a lot of other things about it along the way). If you must talk about it why not instead focus on what better examples of handling this kind of situation have been instead of easy quips about why this didn't go as it should have? Or handling toxicity in online communication since it could easily apply to many of the comments here as well.