When I tell the Windows Terminal team something is simple, I am "misguided"
Another day, another Casey post dunking on my team. Hi!<p>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 apology[2].<p>This blog post is matter-of-fact, but Casey is <i>right</i>. However, he said himself that it was trivial to do this. Is it not acceptable that we use the same language?<p>Casey, I'm sorry. We made a mistake. <i>I</i> made a mistake! We didn't know what we didn't know, and thought we were clever enough to pass for it.<p>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.<p>[1]: <a href="https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-13-release/#new-rendering-engine" rel="nofollow">https://devblogs.microsoft.com/commandline/windows-terminal-...</a> (scroll down under the image)<p>[2]: <a href="https://twitter.com/cmuratori/status/1489406091318349826" rel="nofollow">https://twitter.com/cmuratori/status/1489406091318349826</a><p>--<p>(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.)