When I tell the Windows Terminal team something is simple, I am "misguided"
21–30 of 476 posts
Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#22Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#23Pretty sure the "trivial" in the blog post is sarcastic, or at least slightly self depracating.
It's not a great look to open a blog post with sarcastic comments referring to (unneeded) controversy, though. Regardless if you were right or wrong.
Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#24if it was an open project the narrative would be "reaction to the suggestion was mixed; then it was adopted." Its not like Microsoft is a singular mind here; the poor slobs working there do not deserve to be tarred with all the sins of that name, and vice versa. That said, why suggest anything to Microsoft? I no longer advocate for the dissolution of the company and torment of its employees with the fervor i used to,…
1) 1980-2000 Microsoft was evil. I find 2022 Microsoft to be ahead of Google and Facebook on the ethics front, so YMMV. Microsoft doesn't do much antitrust anymore, is /more/ respectful of privacy than most of the tech industry, and by some measures, is the world's largest contributor to the open source collective. Tools like Visual Studio Code are pretty good too, and run on GNU/Linux. 2) Even with evil companies, c…
In 1977 Bill Gates wrote a public letter saying that software piracy is wrong and developers should get paid; this was highly controversial at the time and launched the hackers-vs-MSFT dichotomy. A lot of people sincerely believed it’s evil to use copyright law to prevent anyone from making copies of software.
40+ years later, evil in the software industry is pretty much “willingly assists in genocide”. All other evil behaviors have been adopted and rehabilitated into a business growth narrative, helped along by Google’s gaslighting slogan “Don’t do evil” which led a generation to believe that anything Google is doing can’t be evil.
Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#251. The linked threads don't support the title written here. 2. Even if this were true, who cares? 3. Microsoft comes across fine. The dev comes across as entitled and petty.
Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#26I 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.
Even in 2022, having worked there, I guarantee that the Microsoft org chart meme [0] is still true. I do agree in-person talking would have helped. [0] https://assets.sbnation.com/assets/2907963/microsoftguns.jpg
Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#27Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#28Looks like Microsoft finally found someone good enough at terminal emulator development to fix the performance issues. I can't shake the feeling that the original Github issue and the heated discussions in there were more Windows Terminal devs not wanting to admit their knowledge gap in this area than impracticality and complexity.
> 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 wording – irrespective of if they were correct.
Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#29that being said, the actions of the ms dev don't paint him in a good light, either.
i'd say theyre both in the wrong in one way or another.
Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#30This 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 apology[2].
This blog post is matter-of-fact, but Casey is right. However, he said himself that it was trivial to do this. Is it not acceptable that we use the same language?
Casey, I'm sorry. We made a mistake. I made a mistake! We didn't know what we didn't know, and thought we were clever enough to pass for it.
Using a texture atlas was a great idea, and we didn't know about it until you told us. We should do better to credit you.
[1]: https://devblogs.microsoft.com/commandline/windows-terminal-... (scroll down under the image)
[2]: https://twitter.com/cmuratori/status/1489406091318349826
--
(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. It also originally contained "I get it, Microsoft sucks, we should all be fired, rah rah rah." As the message evolved, that became more and more out-of-place.)