3 ms·

That's not how I interpretted the github thread and blog post. It seemed like the MS team was saying "yes we know this is one way to solve it, but it's incredib

That's not how I interpretted the github thread and blog post. It seemed like the MS team was saying "yes we know this is one way to solve it, but it's incredibly difficult", and one year later they post "we finally did it and this is how difficult it was". As the author of the blog post mentioned here, the sentence about how "trivial" it was, was actually sarcasm, and the rest of the blog post highlights the technical challenges

jbverschoor 4y ago
That's not how interpreted it.. there's way too much elitism in tech. And also aggregations about how easy or difficult things are. "AI will solve things" -> they have no clue, and just trust it's gonna work itself. "It's difficult to add a field to that form, it'll take 2 weeks" -> usually bs. I read the thread, and I fully agree that it should be a weekend work. So yeah, it's just other devs mismanaging their time, and therefore saying that things take way longer. The issue created 2 days afterwards (https://github.com/microsoft/terminal/issues/10461 https://github.com/microsoft/terminal/issues/10461) starts with the previously suggested solution which didn't make any sense because the original post "didn't understand how DirectWrite works, and yadayadayada". The solution is as trivial as "but just optimize our render pass instead" No sarcasm there. The whole sarcasm is just covering up their own ass 1 day later implementation starts. 2 days after that it was implemented.. > Yep! And I'm entirely on it! So eager to work on an issue created by himself instead of someone else! > Terminal cannot turn away valuable performance work simply on ideological grounds. The "Atlas-Engine" label hasn't been added to the original issue either. It just stinks like people using politics to improve their HR performance review.
- woojoo666 4y ago
  I find it weird that github user cmuratori is willing to write in so much detail about how to do it and how it's only a weekend of work, but doesn't submit a pull request themself. To me, it's rather easy to make requests and speculate about different approaches, but actually implementing the solution can be much more expensive. Not to mention, as some of the other HackerNews threads mention [1], they very well could have already gotten cmuratori's idea from another person (in fact they say they already heard it from alacritty), and it could have already been an idea in consideration but they hadn't fully explored it yet because they chose a different path to try first. The github thread you linked seems to indicate the same thing. For cmuratori to just write a few github comments and then demand credit seems a bit much. Also note that the blog post has been updated to mention cmuratori, although that could just be to appease the outcry. [1]: https://news.ycombinator.com/item?id=31287644 https://news.ycombinator.com/item?id=31287644
pas 4y ago
it turns out it's not difficult, MS is just very bad at this. https://twitter.com/stewartlynch8/status/1522512601443454976 https://twitter.com/stewartlynch8/status/1522512601443454976 https://github.com/microsoft/terminal/issues/10362#issuecomment-862822530 https://github.com/microsoft/terminal/issues/10362#issuecomm...

jbverschoor 4y ago

That's not how interpreted it.. there's way too much elitism in tech. And also aggregations about how easy or difficult things are. "AI will solve things" -> they have no clue, and just trust it's gonna work itself. "It's difficult to add a field to that form, it'll take 2 weeks" -> usually bs. I read the thread, and I fully agree that it should be a weekend work. So yeah, it's just other devs mismanaging their time, and therefore saying that things take way longer. The issue created 2 days afterwards (https://github.com/microsoft/terminal/issues/10461 https://github.com/microsoft/terminal/issues/10461) starts with the previously suggested solution which didn't make any sense because the original post "didn't understand how DirectWrite works, and yadayadayada". The solution is as trivial as "but just optimize our render pass instead" No sarcasm there. The whole sarcasm is just covering up their own ass 1 day later implementation starts. 2 days after that it was implemented.. > Yep! And I'm entirely on it! So eager to work on an issue created by himself instead of someone else! > Terminal cannot turn away valuable performance work simply on ideological grounds. The "Atlas-Engine" label hasn't been added to the original issue either. It just stinks like people using politics to improve their HR performance review.

woojoo666 4y ago
I find it weird that github user cmuratori is willing to write in so much detail about how to do it and how it's only a weekend of work, but doesn't submit a pull request themself. To me, it's rather easy to make requests and speculate about different approaches, but actually implementing the solution can be much more expensive. Not to mention, as some of the other HackerNews threads mention [1], they very well could have already gotten cmuratori's idea from another person (in fact they say they already heard it from alacritty), and it could have already been an idea in consideration but they hadn't fully explored it yet because they chose a different path to try first. The github thread you linked seems to indicate the same thing. For cmuratori to just write a few github comments and then demand credit seems a bit much. Also note that the blog post has been updated to mention cmuratori, although that could just be to appease the outcry. [1]: https://news.ycombinator.com/item?id=31287644 https://news.ycombinator.com/item?id=31287644

pas 4y ago

it turns out it's not difficult, MS is just very bad at this. https://twitter.com/stewartlynch8/status/1522512601443454976 https://twitter.com/stewartlynch8/status/1522512601443454976 https://github.com/microsoft/terminal/issues/10362#issuecomment-862822530 https://github.com/microsoft/terminal/issues/10362#issuecomm...