Live data from Hacker News

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

twitter.com

471–476 of 476 posts

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

#471

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.

    s/years/multiple decades/

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

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

> Using a texture atlas was a great idea, and we didn't know about it until you told us. One is forced to wonder how, in an entire team working on a terminal emulator, no one thought to use the texture atlas. I mean, that's basically how the actual physical terminals the software is emulating worked in the first place. Then, when told about the obvious implementation, the reaction was not to slap one's forehead and s…

They've bragged in the past that the team members are younger than conhost.exe. I think that about sums it up.

It's not a crime to be naive, but lashing out in response is a problem, as we've seen.

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

#473

Earlier quoted context omitted.

I've pointed out flaws to the dev team at MS they were pretty quick about acknowledging it and fixing the problem. There were some showstoppers in the media encoders early on when they were developing win10. The only thing they asked is that I prove the issue was real and as soon as I did they were on top of it. They were also pretty quick and helpful with answering any question I had. I guess it depends on what team…

Reading your post feels good, man. But your last sentence kind of bothers me. Why do you feel they are insulting you now? I think, if at all, someone else was, and kept doing, and still is, insulting them instead. I'm just trying to understand here, thanks. :)

In the last paragraph I indicated that they never insulted me. The very last sentence is referring to the article and that I'm sad to hear that this is the case now for others. When I personally interacted with Microsoft that wasn't the situation I had at all. I had a good experience.

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

#474

Earlier quoted context omitted.

Not sure about the cursor being 1 to the left of where you'd expect but the box behaviour is something you need to specify in your .vimrc otherwise it'll use the default cursor for the terminal. Something like this may be what you're used to: let &t_SI .= "\ [4 q" let &t_EI .= "\ [2 q" You probably also want set ttym=sgr if you want mouse interactions to be sent properly.

Yep that was it. Many thanks.

Any time, it's all a bit arcane really I'm not sure how anyone is supposed to figure it out without having been told themselves.

Love your username by the way!

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

#475

Earlier quoted context omitted.

> I am open for being corrected No. No you're not. Because you keep shifting goalposts and ignoring inconvenient truths. First you claimed that "almost none of the techniques "he" brags about can be applied to a real terminal". To which I linked and quoted Windows Terminal team: "We actually took the same approach Casey suggested. A lot of terminals implement it that way." Then you shifted the goalpost to saying "We…

> > I am open for being corrected > No. No you're not. Because you keep shifting goalposts and ignoring inconvenient truths. I still am. Please submit a PR to refterm to that implements the VT sequences I mentioned above, until then I must continue to believe that you just repeat what other people say, without using your own brain. Shifting goalposts is probably not the best wording here. I keep listing arguments. >…

He never claimed refterm was a fully working terminal ready to use. He said it was a renderer. The entire point of refterm was:

     Windows Terminal is slow at rendering things
     Yes, rendering is a hard problem worthy of a doctoral research project
     No it's not, you literally just use a glyph atlas
     You are naive
     *writes refterm to demonstrate glyph atlas*
You keep complaining that it's not a fully working terminal. Casey, on the other hand, writes:

"These features are not designed to be comprehensive, since this is only meant to be a reference renderer, not a complete terminal."

https://github.com/cmuratori/refterm#feature-support

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

#476

Earlier quoted context omitted.

> > I am open for being corrected > No. No you're not. Because you keep shifting goalposts and ignoring inconvenient truths. I still am. Please submit a PR to refterm to that implements the VT sequences I mentioned above, until then I must continue to believe that you just repeat what other people say, without using your own brain. Shifting goalposts is probably not the best wording here. I keep listing arguments. >…

He never claimed refterm was a fully working terminal ready to use. He said it was a renderer. The entire point of refterm was: Windows Terminal is slow at rendering things Yes, rendering is a hard problem worthy of a doctoral research project No it's not, you literally just use a glyph atlas You are naive *writes refterm to demonstrate glyph atlas* You keep complaining that it's not a fully working terminal. Casey,…

Exactly. Therefore you cannot compare a renderers performance with some other that has a fully functional VT backend attached. The comparising result is meaningless. His renderer is good, but the VT throughput performance claims he makes are wrong. For that to be fair, he should not take shortcuts in functionality.
Post reply on HN