I feel like the suggestion to just delete your Meta account is unhelpful and even harmful in some situations. I know a lot of us in this field don't mind having a small social circle, but for us that struggle to even have that, or that the process of doing that, requires you to be as open and reachable as possible to make it easier to create or maintain friendships, this often requires having an account to use Messenger (I know regionally this may differ).
Being difficult in this way, when most other people, particularly non technical people, don't have a problem with this, in my experience significantly hurts your opportunities and limits the types of people you socialize with in real life, which I think can eventually be harmful.
If this is still the same install that you've been using since 38, you might find a clean install resolves some issues (whether or not your upgrade got botched). Also helps me get rid of software I installed that I don't use anymore, which I feel is relevant to this article. But part of why I love Silverblue so much is I don't have to worry about upgrades getting botched and fwiw as well, I haven't noticed any of those bugs on 44 across several very different machines.
Not sure popularity necessarily suggests it's good, but possibly just what people have most heard of or is easiest to setup with. This is going to be even more true now that Claude subscriptions are going to be essentially vendor locked.
Comparing this project to is-odd seems very disingenuous to me. My understanding is this was the only way you could use llama.cpp with Claude Code for example, since llama.cpp doesn't support the Anthropic compatible endpoint and doing so yourself isn't anywhere near as trivial as your comparison. Happy to be corrected if I'm wrong.
I would hazard a guess that it's because there's been many debates about contributing PRs that might be perceived as AI slop. Not saying that's the case here, but it's possible the fix might be a poor one, not follow the project's guidelines, or one which the contributor doesn't fully understand, but doesn't care because it fixed the issue. I would guess the better approach would be to submit a bug report with the same information the LLM used, and maybe suggest there the fix the LLM provided. Unless this really was a tiny patch and none of the above concerns applied.
The prompt processing times I've heard about have put me off wanting to go that high with memory on the M series (hoping that changes for the M5 series though). What's the average and longest times you've had to wait when using opencode? Has any improvements to mlx helped in that regard?