Live data from Hacker News

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

twitter.com

91–100 of 476 posts

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

#91
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…

I'm impressed you could write this without the self-awareness to realize this only makes your team look worse.

The idea that vaguely saying sorry to an abstract community should resolve this entire issue is repulsive. Merely stating an apology does not thereby grant you forgiveness.

I had a neighbor who once tore up my yard doing construction. They apologized profusely, but outside of words never made any meaningful recompense. If I complain about the damage am I in the wrong simply because he utter some words of apology?

The tone here sounds like you're more annoyed that Casey was right and wish you could go back to feeling clever.

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

#92
post #42
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…

[deleted]

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

#93

Issue: Feeling bad after interaction with OSS developer at . Steps to reproduce: 1) Report a bug. 2) Get called dumb by developers at . 3) Demonstrate that it is, in fact, a bug with examples, test cases, and offer a potential fix/PR. 4) Hear that it’s being “handled internally”. 5) Wait for the blog post re-iterating what they called dumb, talking about how great the team is that fixed it, and see your demonstration…

And the Windows Terminal team reeks of this. There's so many blog posts saying look, we're so smart because they're reimplementing something both Linux and macOS had for *years*, as if the whole world of CLI was waiting for their savior.

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

#94

I really wonder why OSS developers often have so big ego issues. I mean I get it, attribution is nice and all, but trying to force attribution for evey small idea you might have had in your life by trying to rally the public against "the evil corporate enemy"? Really? How low can you sink

No post body was provided.

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

#95
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…

Any response to his claim that the author of the blogpost was talking about Windows Terminal in his Discord? The license of Casey’s project would be an issue if you guys used it.

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

#96
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…

> I'll admit that we didn't list him by name, but neither did we list the other handful of folks involved

It's only an apology in the manner of soulless corporate jargon then. A generic statement following a personal/directed insult does not count as an apology.

Edit: also the following

> (Note: I've iteratively edited this post, as it was originally a one-sentence diatribe written in anger. I originally asked, "I just don't know what else he's asking for here. Credit? Us to die screaming?" It was not a good look.)

I think your comment and it's different iterations demonstrated very well how you guys (still) feel about this.

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

#97
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.

When you're a global company serving a billion plus users on every continent, you can't expect face-to-face discussions with everyone who reports a bug or makes a feature request. You need to be able to handle written feedback.

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

#98
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…

Thanks for your response; you're getting a lot of flack here, even repeated suggestions of ESL, by people who I feel have unreasonable expectation of perfection of others that I doubt they'd be able to fulfill 100% in every facet of their own life.

English is indeed not my first language, but I've lived in North America for 25 years and stakeholder communication is part of my job description. "I did something wrong; please accept my apologies" to me is boiler-plate standard, sufficient, acceptable way.

Your blog post goes way past that! It says "We caused the kerfuffle". Even "We were Wrong", explicitly! I for one understand your frustration and probably real question of "What else do you want from us - keel over and die?" - it's just that humanity is not an acceptable feature to show from people HN wants to hate on already.

That's OK though. Their reaction here will simply mean we'll get less sincere humane posts like yours, and more corporate-sanitized meaningless PR, which I'm sure will make those very same people much happier. And yes that's a pointed /s :-)

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

#99
post #75
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…

> I just don't know what else he's asking for here. Credit? Us to die screaming? ... We get it, Microsoft sucks, we should all be fired, rah rah rah. Someone is upset and venting. This comment comes across to me as "Ugh we already said the right words. Their distress is so inconvenient to me, why isn't it stopping?" EDIT: Typically in this community we denote when a comment has been edited to change a critical piece…

> I'm detecting very little genuine authentic empathy

Welcome to Microsoft!

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

#100
post #45

Earlier quoted context omitted.

> 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.

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. Seems pretty sincere and decent to me.

Nah, this is the pestilent child response when they are wrangled into giving a "sincere" apology.
Post reply on HN