281–290 of 476 posts
Earlier quoted context omitted.
Devs over and underestimate effort all the time
Sure but in this case it was grossly over-estimated compared to the under-estimated side. Casey did the implementation [1] to prove the point and also made explanatory videos [2] of it. [1] https://github.com/cmuratori/refterm [2] https://www.youtube.com/watch?v=hxM8QmyZXtg&t=1052s
Earlier quoted context omitted.
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.
When CMD is your benchmark... (In all fairness, PowerShell has a lot of good ideas)
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.
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.
Earlier quoted context omitted.
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.
When CMD is your benchmark... (In all fairness, PowerShell has a lot of good ideas)
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.
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.
> Baffles me that people think sarcasm is a good way to communicate on the internet.
The subtext here is that the idea of using sarcasm on the internet should be obviously stupid to everyone, thus you're stating anyone who exercises it is stupid. That or you're clearly smarter than everyone else.
> You are begging to be misunderstood, either accidentally, or maliciously.
Thus, if you're using sarcasm you're either stupid or evil.
Was your intent to insult people?
Sarcasm and irony can be effective means of communication, the same as exaggeration. Communication is hard and people posting on the internet don't() invest much thought most of the time.
* Typo
Earlier quoted context omitted.
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…
Firstly, I think people are making a mountain out of a molehill. The article remains comprehensible on the whole. It’s a good article. 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 u…
Earlier quoted context omitted.
Caseys suggestions were pointless because Direct2D is fast at drawing western text without coloring? Didn't casey open an issue because the terminal was slow with coloring ? It seems like you managed to optimize Direct2D with your 'glyph cache' pixel shader but that doesn't mean caseys suggestions were pointless.
I didn't say they were pointless anywhere. They were anything but. I did say however: If we had figured out a way to solve the issue while we continue using Direct2D, we would've definitely sticked with Direct2D. Since there was no solution, there was only one other way to solve it and it's a way that has many other terminals already do it.
Despite the apologies you or your team have given, you continue to denigrate and downplay. First, Casey's suggestion "doesn't help much"; then, "Casey's suggestion wasn't unique". And so on. Casey suggested a solution, spent time proving it was easy, and you even used the suggested solution to good effect, and you're still trying to downplay Casey's contribution or involvement.
If Casey hadn't kept pushing, it's doubtful you'd even have gotten around to doing this, so some actual credit is warranted, along with perhaps a real apology.
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…
Do not let your sarcasm/irony out of the articles, I've enjoyed.
Earlier quoted context omitted.
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.
When CMD is your benchmark... (In all fairness, PowerShell has a lot of good ideas)
It could just be a coincidence/confirmation bias, so I wonder if there's actually something to that.