OK I've been biting my knuckle about this farce for the past few weeks but I keep getting tagged into this, so I guess I'm writing a short statement on this whole mess after all. https://twitter.com/neo_ar218/status/1413419982873055233 …
-
-
The passive aggressiveness sent your way was indeed impressive.
-
I also don't understand why there even was a thread. And in that thread, I both apologized for being "terse" (which I didn't think I was), _and specifically stated if they didn't think this benchmark was useful, that they should feel free to close the ticket_.
- Show replies
New conversation -
-
-
This happened to me in real life also some times.
-
Sorry to hear that :(
- Show replies
New conversation -
-
-
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.
-
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.
- Show replies
New conversation -
-
-
I’ve heard the same feedback from other maintainers. Casey didn’t care thats its “open for spectators” MS product and was just filling in bug report. Both valid? Remember https://en.m.wikipedia.org/wiki/Law_of_Jante … for opensource. Dont expect anything from corp os “till 2023” at least
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.