Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

twitter.com

Post reply on HN
Print view View original

41–50 of 476 posts

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

#41

Post by [deleted] »

TrueTom wrote: post #35
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…

It seems you have posted the wrong link because there isn't really an apology?

[deleted]

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

#42

Post by doix »

TrueTom wrote: post #35
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…

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, everything would be resolved. Instead it's just little snide remarks back and forth. It's a shame, I really like Casey, and he was definitely right, but it's probably time to move on.

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

#43

Post by Tronchenbiais »

TrueTom wrote: post #35
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…

It seems you have posted the wrong link because there isn't really an apology?

Just below the screenshot.

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

#45

Post by ddalex »

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.

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

#46

Post by [deleted] »

TrueTom wrote: post #35
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…

It seems you have posted the wrong link because there isn't really an apology?

[deleted]

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

#47

Post by mns »

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…

Wow, that's sure a weird way to post something on behalf of your company. Curious how long will it take to delete this message, seeing how it was written mostly in the heat of the moment.

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

#48

Post by rglullis »

BaseballPhysics wrote: post #32
deburo wrote: post #12

I blame the disagreement on online communications. Can you imagine this conflict lasting this long if these guys had been talking about it in person over coffee? They would probably behave with much more restraint and respect for each other.

Careful, that's starting to sound like an example of a downside to remote work, which is a touchy topic these days...

That's a downside of exclusive reliance on written communication, not of remote work. You can avoid this with a phone call or a "can we pair for a bit?" session as well.

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

#49

Post by Robin_Message »

lallysingh wrote: post #38
TrueTom wrote: post #35

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…

I have no skin in the game, but I don't think the paragraph above meets the specification claimed by the GP: "we apologized[1] pretty frankly to Casey and everyone else involved in this discussion."

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

#50

Post by lelandfe »

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.

If it was your code they were talking about, you may feel differently.

Blunt, hyperbolic statements like "massively overcomplicated" can feel like a shot across the bow when someone is talking about code you wrote. Kindness and gentleness go a long way in OSS.

Post reply on HN