161–170 of 476 posts
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
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…
Well, it wasn't a real apology. It was "We hope you accept our apology
When you apologize, you say "I am sorry [insert other words of explantion]." Then you can say "We hope..."
What you did simply refers back to an apology that wasn't actually made. Considering that he was correct in saying the problem was simple, his tone was not actually combative, it accurately characterized the problem. So you belittled him & insulted him, and as you admitted you then failed to give credit where due to him & others. He has a career as well. Wouldn't it be nice for him to be able to pad his Vitae with a win on something like this?
Then your initial response he was, as you said, "not a good look". The edited post is better, but still not very good.
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?
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…
Clearly some egos have been bruised, but that's the reality of open source. You aren't just dealing with pre-screened colleagues. Some higher management should step in to mediate and cool things off.
Absolutely unsurprised that the Windows Terminal team wasn't focused on this or didn't pull in, say, a rendering expert. Microsoft is very siloed.
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 week's blog post refers to them as a "community member" [of Microsoft]. Such a self aggrandizing term.
Someone reported a bug on github. Your team dismissed them and peppered them with deflective words to pretend that the team is making a safe space for employees that don't care at all.
Your edits are getting closer.
Honestly people, just don't use the product. A putty session to a Linux box still beats anything Microsoft can offer.
Something the Microsoft API team did irked me slightly. One day the Microsoft 360 API (used for email) seemingly stopped working. After a whole week of troubleshooting and discussion with other devs around the planet I fixed the issue. New headers had to be included. It was a one line fix that stole a week of my life. The API had changed. I could have been ok with this but when I made a post on the repo explaining the fix and that I had no idea why it had even changed, instead of a thank you- a Microsoft API dev chimed in to say it was a trivial change and didn’t see what everyone was so upset about. Knowing no documentation had been updated and every system around the planet had been broken for probably a week that depended on it. No apology no gratitude. I can handle that. But an insult to say I was being impertinent and overblowing the importance.
Well I never forgot it, and eventually this stuff comes out. I hazard to say there are toxic dangerous people in every major company I just don’t understand why these people aren’t cautioned as soon as these public incidents happen it’s as if no one is really watching the behaviour in the irc channels or repos but are instead focusing on internal metrics which in my opinion don’t measure the devastation cause by these bad apples - who should atleast be checked up on.
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…
Quoted post unavailable.
https://news.ycombinator.com/newsguidelines.html
> Throwaway accounts are ok for sensitive information, but please don't create accounts routinely. HN is a community—users should have an identity that others can relate to.
Earlier quoted context omitted.
It does seem vague though. It’s almost akin to saying “I could’ve done this in half the code”. Well add your PR then.
They did, they implemented a crazy fast terminal renderer (that still supports advanced features like right-to-left languages in Unicode, etc.) from scratch in about 3,000 lines of code just to prove their point: https://github.com/cmuratori/refterm
This is a situation where tu quoque really doesn't smell like a logical fallacy. There is a lot of fuss about "being right" over "being helpful."