My #1 recommendation on the actual question asked is to get over idol worship and especially caring about what "genius programmers" think and spend that energy on persistence, being a better collaborator, and drilling down until the answers make sense.
-
Show this thread
-
As for the whole terminal tale, I think Casey dropped the ball big time by getting condescending and grandiose, when e.g. Martins had diagnosed several much simpler and smaller-scope in the same thread that seemed eminently-fixable and not politically tricky.
4 replies 4 retweets 99 likesShow this thread -
There was an opportunity to try and get started on that stuff, build rapport, and then later try and get them to work on bigger stuff, but instead it turned first into a shouting match and now some kind of crusade. What a waste of everyone's time.
6 replies 3 retweets 76 likesShow this thread -
Replying to @rygorous
I like how I was condescended to many times in the github thread, over and over, but when I eventually stopped being polite, I am the one who is blamed. It's pretty great.
4 replies 1 retweet 35 likes -
Replying to @cmuratori @rygorous
I don't think this is about blaming anyone. It's just that the way it was handled is not the shortest path to coax the terminal team (or the 1 actual coder there) to prioritize it. The gap was an actual abys (talks abou PhD). Bridging it takes time, Twitter is not the tool.
1 reply 0 retweets 0 likes -
Well separately I would also like it to be acknowledged that this was a customer bug report? I am the one who has paid a lifetime of $200/machine licenses for Windows, and I filed a bug report with a complete benchmark repro case.
2 replies 0 retweets 12 likes -
Why the onus is placed on me to manage the team's emotional state, to be diplomatic, or whatever else is projected on me, is even more frustrating. This was Microsoft _responding to a customer_. It is not like I am on their team, at their company, or am supposed to be friends.
2 replies 1 retweet 18 likes -
But yet people happily dismiss their behavior and criticize mine, because that is where we are at now. Fantastic.
2 replies 0 retweets 9 likes -
Replying to @cmuratori @rygorous
1/2 What you did was immensely valuable, both as a wake up call to those who are accustomed to slow programs and as a usual top notch Casey level educational material. Terminal team's response is just sad. The note on the reproducer being GPL is pure WTF.
1 reply 0 retweets 1 like -
2/2 Twitter shouting match with groupies polarizing sides is what is not helpful means to an end. Whether you or anyone should be spending time gently coaxing the company to do something is highly debatable though. Obviously you shouldn't if you could leave the company's product.
1 reply 0 retweets 1 like
Well the kicker is I don't use this product. I don't care about Windows Terminal even a little bit. I just happened to have investigated the slow performance because I needed to know why refreshes were so slow in text mode SCG, so I thought I should let them know!
-
-
That's the last time I do that, I can tell you that right now!
1 reply 0 retweets 5 likes -
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
