[KennyBlanken]

> We admit this feature began with a kerfuffle we caused in the summer of 2021. When confronted with being told our rendering pipeline had terrible performance, we turned inward. We relied on our existing experiences and we leaned heavily on our partner teams’ work to conclude the DirectWrite general purpose renderer was the best fit for our product. We were wrong. As such, we dedicate this experimental renderer to the community as an olive branch. We know we have so much more to learn, but we hope that you will accept our apology and understand we’re humans behind this product with a capability and willingness to learn from our past mistakes. Thank you for sticking with us. We strive to make this an experience we can all learn from to not only improve ourselves, but to improve our product and delight you all.

That is "combative, thin-skinned and hostile to outsiders"?

They say they caused it. They explain the cultural attitude that led to it. They plainly state they were wrong.

The "We get it, Microsoft sucks, we should all be fired, rah rah" is responding to the typical outraged rants from immature people who think it's cool to leverage extreme levels of criticism at people and teams who work in large corporations.

[ineedasername]

>That is "combative, thin-skinned and hostile to outsiders"?

Yes. They reference an apology, didn't actually make one, and it was roughly a year after they were combative, thin skinned, and hostile to outsiders. So their words now don't negate the fact that they were actually those things.

And the original now-edited response here was itself still combative, so I don't have much reason to believe they've actually changed rather than just trying to put a nice public face on about it.

[KptMarchewa]

They do this because OP keeps twisting the blade. He was right, now whatever, maybe find another target.

[ineedasername]

I don't see it as twisting the blade. He's calling them out for having insulted him and then making a half-hearted (at best) apology without giving proper credit (which the MS employee up the thread admitted they should have actually done.)

[Aeolun]

I dunno. I can read that as a ‘sorry’, but it kinda feels like ‘we know we were being assholes but we’ll be good from now, forgive us please’ kind of thing.

There’s too many fluffy words in that.

“We were dicks to the person (people) that pointed out a better way. We didn’t truly investigate the proposed solution at first, we acted combative,

and we were wrong.

We’ve now implemented the proposed solution in an experimental renderer that you can all use and we’ll try to do better from now.”

[rob74]

I don't know about others, but that does sound like a real apology to me. At least they plainly write that they were wrong and not only "sorry for how this was handled" or something similar. I'm really curious what more you could expect...

[brothir]

Specifically naming Casey and specifically apologizing for the specifics of how it unfolded. The fact that a team member went into Casey's Discord to harass him would be one example to apologize for.