When I tell the Windows Terminal team something is simple, I am "misguided"

Post by 0des » Fri, May 06, 2022, 1:42 PM UTC

doix wrote: post #42

TrueTom wrote: post #35

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…

Post by dark-star » Fri, May 06, 2022, 1:42 PM UTC

Post by gimme_treefiddy » Fri, May 06, 2022, 1:42 PM UTC

10000truths wrote: post #31

lelandfe wrote: post #28

Earlier quoted context omitted.

To be fair, the GitHub commenter in question had made this statement: > It really seems like most of the code in the parser/renderer part of the terminal is unnecessary and just slows things down. What this code needs to do is extremely simple and it seems like it has been massively overcomplicated. I think they deserved a better response from Microsoft, but I also probably would not have responded favorably to that…

> I also probably would not have responded favorably to that wording – irrespective of if they were correct. Why not? I see nothing wrong with this sort of feedback. It's blunt, but constructive.

Post by sirbranedamuj » Fri, May 06, 2022, 1:43 PM UTC

ddalex wrote: post #45

DHowett wrote: post #30

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…

> except to note that it was not an apology at all. Ctrl-F there doesn't show a single "sorry" in the text. Or "Casey" for that matter. Why is it so difficult to say: "Casey, we are sorry, you were right and we were mistaken.". Instead there is a nebulous ~extended a branch to community and hope to accept our apology~ (paraphrasing) without offering an apology in the first place.

Post by beart » Fri, May 06, 2022, 1:44 PM UTC

10000truths wrote: post #31

lelandfe wrote: post #28

Earlier quoted context omitted.

To be fair, the GitHub commenter in question had made this statement: > It really seems like most of the code in the parser/renderer part of the terminal is unnecessary and just slows things down. What this code needs to do is extremely simple and it seems like it has been massively overcomplicated. I think they deserved a better response from Microsoft, but I also probably would not have responded favorably to that…

> I also probably would not have responded favorably to that wording – irrespective of if they were correct. Why not? I see nothing wrong with this sort of feedback. It's blunt, but constructive.