Seems like a misleading title to me.
I'd summarize this more as "Microsoft employees initially disagree with dev's idea, but eventually admit he was right."
51–60 of 476 posts
Seems like a misleading title to me.
I'd summarize this more as "Microsoft employees initially disagree with dev's idea, but eventually admit he was right."
Earlier quoted context omitted.
It seems you have posted the wrong link because there isn't really an apology?
"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 th…
Another day, another Casey post dunking on my team. Hi! This tweet misses the mark only a little bit; in a previous blog post, we apologized[1] pretty frankly to everyone involved in this discussion. I'll admit that we didn't list him by name, but neither did we list the other handful of folks involved. We should have. In turn, Casey rightly did not acknowledge it except to tell his followers that it was not a real a…
Also, good apologies come with admission of fault and steps you'll take to make sure you don't make the same mistake again.
Another day, another Casey post dunking on my team. Hi! This tweet misses the mark only a little bit; in a previous blog post, we apologized[1] pretty frankly to everyone involved in this discussion. I'll admit that we didn't list him by name, but neither did we list the other handful of folks involved. We should have. In turn, Casey rightly did not acknowledge it except to tell his followers that it was not a real a…
Typically, when apologizing, you should name the person you are apologizing to. Otherwise, they might do something like not acknowledge your apology.
Earlier quoted context omitted.
It seems you have posted the wrong link because there isn't really an apology?
> 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. What more really needs to be said? Feels like one of those times where if everyone just sat around at a pub with a beer…
Another day, another Casey post dunking on my team. Hi! This tweet misses the mark only a little bit; in a previous blog post, we apologized[1] pretty frankly to everyone involved in this discussion. I'll admit that we didn't list him by name, but neither did we list the other handful of folks involved. We should have. In turn, Casey rightly did not acknowledge it except to tell his followers that it was not a real a…
This response shows how little you value users feedback (and how unafraid of them you are). Probably should leave this kind of thing to your developer relations team...
Earlier quoted context omitted.
It seems you have posted the wrong link because there isn't really an apology?
> 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. What more really needs to be said? Feels like one of those times where if everyone just sat around at a pub with a beer…
Well if I were to write an apology "frankly to " I would probably mention by name in the apology.
No wonder why they didn't know what they were doing
So that kind of behavior doesn't surprise me
What's even more surprising is it's the same for everything windows related, including windows 11, performance issues all over the place, nobody acknowledge it, and whenever they face criticism and complain, it's the ugly trolls!
Sometimes i feel like some managers doesn't want to give up their position and salary, so they surround themselves with tasteless people
Culture and hiring problems at microsoft, as usual, apple is being hit by the same issues these days, just like google and facebook
Lot of money to be made in these positions, it always attract the wrong people
Another day, another Casey post dunking on my team. Hi! This tweet misses the mark only a little bit; in a previous blog post, we apologized[1] pretty frankly to everyone involved in this discussion. I'll admit that we didn't list him by name, but neither did we list the other handful of folks involved. We should have. In turn, Casey rightly did not acknowledge it except to tell his followers that it was not a real a…
> We get it, Microsoft sucks, we should all be fired, rah rah rah.
> I just don't know what else he's asking for here. Credit? Us to die screaming? The blog post is matter-of-fact, and Casey is right: however, he said himself that it was trivial to do this. Is it not acceptable that we use the same language?
Your "apology" really is anything but. If anything you and your team come off as combative, thin skinned and hostile to outsiders. But, you do you bro.