If that's the root of the issue though, most of the article ("no one will get promoted for prioritizing that at Google.", "the go team has not prioritized it", etc.) is wrong.
I think the blog author is implying as much as he can, without directly accusing, that he believes that https://github.com/shinnn was responsible for the bad code, not a random hack.
No. He works at Google, and during 2015 he temporarily provided support to internal LuaJIT users there and made many contributions in the process, but working on LuaJIT is not his job. (The world world be a better place if it were!)
From what I can see, @jart had spent a considerable amount of time on this problem and had posted an interesting-but-not-production hack to it (https://github.com/ggerganov/llama.cpp/commit/5b8023d9354010...) on March 17th, which they had also excitedly posted about on Twitter.
This was 2 weeks prior to @slaren's contribution (https://github.com/slaren/llama.cpp/commit/fc685122f95f212d1...) on March 29th, so in a sense, it's quite possible that what you've just shown is that @slaren saw that @jart was working on mmap support, worked out a cleaner solution and then wasn't happy with only being a co-author -- for their contribution, they believed that they must be the only person mentioned on the PR: although this is weird, since I don't think they even have a public profile, so maybe instead the truth is that they weren't comfortable with working with somebody that hypes up any changes they've worked on for popularity?
I don't think saying "my changes" on Twitter and other social media means what you suggest it does as is it is just informal speech to refer to things you've worked on with "my", and particularly when you see the times this was expanded (e.g. "yesterday my changes to the LLaMA C++ file format were approved") it seems more reasonable than it does without this context.
So, guy who wrote GitHub and a ton of open source stuff is ousted from his own company and sacrificed for a person whos biggest accomplishment in open source is JavaScript for Cats? https://github.com/nrrrdcore/javascript-for-cats
This does not sound plausible, more like the work of an Internet troll. The user's GitHub handle translates as "Fuck you all, damn it!". When asked to provide evidence, he comes with excuses in the linked thread. He has filed some issues before with the same project, some of which got closed as dupes. My take is he was dissatisfied with the response from the GitHub community and came up with this story to discredit the project.
This person isn't a grapheneOS developer. I'm unsure why people keep saying that.
In the GOS chatrooms this article has come up a few times but I've seen them say they don't know why people keep saying this person is a GOS dev. I mean look at the author's github. They sponsor the lead dev but have no commits or forks in the project to show for.
He does have a GitHub account[0]. He successfully founded his own company. Entries from his blog also made the frontpage on HN several times[1].
You, on the other hand, do not have a GitHub account tied to your HN account, or any other records of your achievements, for that matter. You also don't seem to have made any meaningful contributions. But people still took the time to read this comment.
The author's history of contributing to OSS projects shouldn't be relevant here. You shouldn't use it to attack his claims. If someone wants to read the article, they can read/evaluate it based on their personal opinions/knowledge.
There was no drama as far as I recall, just complaints that he wasn't agile enough or something like that. The different project is Gogs https://gogs.io/ and its author is Joe Chen ('unknwon').
Besides some badly credited forks, I don't see the problem here. He's forking projects on GitHub and expanding on them. As for the stuff about him taking credit for Google Translate, I think it's being taken maliciously for no reason, he just made a node.js wrapper for the Google Translate API -- in fact that's what most of his projects seem to be about, taking popular projects and making them node.js compatible. Nothing wrong with that as long as he doesn't try to sweep the original authors under the rug.
What do you personally have against him, posting this on HN and reddit?
If that's the root of the issue though, most of the article ("no one will get promoted for prioritizing that at Google.", "the go team has not prioritized it", etc.) is wrong.
reply