I really hate when fellow devs say things are "simple" like Casey Muratori said in the first place. Nothing is simple in the software (and hardware) world! If something seems simple then most likely because smart people have written libraries for you that abstract the hard part away. It also shows a certain arrogance to call a topic "simple", because it is supposed to show the audience that you are an incredible expe…
Maybe I’m nitpicking since it’s OSS, but sometimes it’s not even the code. From the outside it seems like a few lines of code but internally there’s a whole org and OKRs and what not.
Issue: Feeling bad after interaction with OSS developer at . Steps to reproduce: 1) Report a bug. 2) Get called dumb by developers at . 3) Demonstrate that it is, in fact, a bug with examples, test cases, and offer a potential fix/PR. 4) Hear that it’s being “handled internally”. 5) Wait for the blog post re-iterating what they called dumb, talking about how great the team is that fixed it, and see your demonstration…
You're a liar. The entire thread on github [1] shows that it is a technical discussion about the unacceptably slow performance of virtual terminal sequences in Windows. Solutions are kicked around and debated until a Microsoft person steps in and calls what is essentially a weekend fix a 'doctoral research project' and accuses Casey of being 'combative'. Casey is rightly annoyed by this, closes the bug report and goe…
Removing a credit or a reference is probably the worst way to add succintness to an article. It's literally saying "the contributions of people whose work I based my work on is less important than the least useful sentence in describing my work".
I'm not sure editing the article would be the proper thing to do at this point. Someone else suggested to edit in 1-2 weeks for possible future readers. I can add back the sentence where I accredit Alacritty for the general, underlying algorithm/idea then, because that's where I heard about it first. There isn't really any other alternative, performant way to implement GPU-accelerated terminals, so I don't think hear…
Anyone who knows anything about Casey Muratori knows that nice and humble are not usually words associated with him. That is not to say the devs he is calling out are in the right. Frankly, I just see a bunch of combative assholes arguing with each other.
This is just a purely insulting comment. Name calling and dismissing valid complaints as that "one time he was right"
Quoted post unavailable.
No, this is just a temp account because I mainly lurk HN. Given your previous tone, I wouldn't suggest accusing others of being part of an "angry mob".
To be honest, this tweet comes across as incredible unproductive behavior in an open source project. If I were the MSFT guys, I just wouldn't be responding to community members who behave like this.
Thank you! It has been absolutely mind-boggling going through the comments.
If I were a Microsoft exec and came through this mess I would say fuck Open Source.
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…
The problem that the poster has is that his input is basically being dismissed. He was too 'overconfident' with his 'opinion'. But it is exactly what has been implemented. It's basically this scenario: > "You don't understand, it's very very hard, next to impossible, to create a website where you can leave an email address. i think you should reread all the RFCs and a bunch of programming books. You have no right to…
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