261–270 of 476 posts
Hi! I'm the person who wrote that blog post. If you have any questions whatsoever, please let me know! English is not my native language and "The solution is trivial" was meant sarcastic. The solution isn't trivial at all, nor is it complete, because solving the corner cases is complex. I'd also like to mention ahead of time that DirectWrite/Direct2D is very fast at drawing western (Latin) text without coloring (>200…
Earlier quoted context omitted.
Perhaps leave sarcasm out of technical blog posts, or add a footnote to indicate sarcasm? I couldn't tell you were being sarcastic and it seems others couldn't as well. I only found out through this comment. Text is the worst medium for sarcasm since sarcasm is often signaled by vocal inflection or body language, neither of which are present in your post.
I'll try to avoid sarcasm in the future. What I haven't understood yet is what significance "The solution is trivial" being sarcastic or not has on the article itself. I understand it's reflecting poorly on it due to what I said earlier, but is there something that makes the article harder to understand due to this? (I realize this question sounds a bit rude, but I'm genuinely curious and I don't know how else to phr…
What is presumably meant is the following: sarcasm and irony require a lot of skill and nuance to get right, precisely because they can be understood as saying something along with its inverse. More often than not, a sarcastic written comment will divide the audience into people who understood it to say P and those who understood it to say !P. This is especially true when your audience is large, culturally diverse, and (on average) rather literal-minded.
But don’t beat yourself up too hard. It’s a good article by any measure, and even more so for someone who is not a native English speaker.
Hi! I'm the person who wrote that blog post. If you have any questions whatsoever, please let me know! English is not my native language and "The solution is trivial" was meant sarcastic. The solution isn't trivial at all, nor is it complete, because solving the corner cases is complex. I'd also like to mention ahead of time that DirectWrite/Direct2D is very fast at drawing western (Latin) text without coloring (>200…
if it was an open project the narrative would be "reaction to the suggestion was mixed; then it was adopted." Its not like Microsoft is a singular mind here; the poor slobs working there do not deserve to be tarred with all the sins of that name, and vice versa. That said, why suggest anything to Microsoft? I no longer advocate for the dissolution of the company and torment of its employees with the fervor i used to,…
1) 1980-2000 Microsoft was evil. I find 2022 Microsoft to be ahead of Google and Facebook on the ethics front, so YMMV. Microsoft doesn't do much antitrust anymore, is /more/ respectful of privacy than most of the tech industry, and by some measures, is the world's largest contributor to the open source collective. Tools like Visual Studio Code are pretty good too, and run on GNU/Linux. 2) Even with evil companies, c…
> is /more/ respectful of privacy than most of the tech industry
What a great example of "damning with faint praise". If you have to compare to Google and Facebook to look good, they're probably still evil.
> Microsoft doesn't do much antitrust anymore
much
Looks like Microsoft finally found someone good enough at terminal emulator development to fix the performance issues. I can't shake the feeling that the original Github issue and the heated discussions in there were more Windows Terminal devs not wanting to admit their knowledge gap in this area than impracticality and complexity.
To be fair, the GitHub commenter in question had made this statement: > It really seems like most of the code in the parser/renderer part of the terminal is unnecessary and just slows things down. What this code needs to do is extremely simple and it seems like it has been massively overcomplicated. I think they deserved a better response from Microsoft, but I also probably would not have responded favorably to that…
I will say, looking through the Windows Terminal GH repo, their whole page seems unnecessarily curt in tone: >I built and ran the new Terminal, but it looks just like the old console >Cause: You're launching the incorrect solution in Visual Studio. I realize that comforting language isn't a priority for a lot of devs/documentation writers, but it's always good to keep in mind that we are dealing with other people rea…
This is worse than it looks, since the person who wrote the blog post is the same person who insulted the dev, and is the same person who joined that dev's related discord under a pseudonym. [1] [1] https://twitter.com/cmuratori/status/1522471966929653761
This goes against Microsoft’s community engagement policies. I hope Leonard reflects on his actions and makes better choices in the future.
Earlier quoted context omitted.
Baffles me that people think sarcasm is a good way to communicate on the internet. You are begging to be misunderstood, either accidentally, or maliciously.
If you limit your communication online to a subset that cannot be willingly or unwillingly misunderstood, then you will say nothing at all. People's capacity to misread is infinite.
Hi! I'm the person who wrote that blog post. If you have any questions whatsoever, please let me know! English is not my native language and "The solution is trivial" was meant sarcastic. The solution isn't trivial at all, nor is it complete, because solving the corner cases is complex. I'd also like to mention ahead of time that DirectWrite/Direct2D is very fast at drawing western (Latin) text without coloring (>200…
It’s just poor form, why make an excuse in the first place? You can just say this was a mistake and try to be better next time.