I don't agree that using something in a very specific environment is the same as a wide release.
I trust readers will either know the backstory or read the articles I link to. Such is life if they don't.
Do you think it would weaken the article?
When I said it would improve the credibility I did mean it. My instinct on reading the article this morning was "this person doesn't know that Claude Code runs on Bun, which weakens their credibility in presenting the argument they are making here."
You could argue that the release tag isn't important - but at the top of this comment thread a member of the team confirms they delayed the release to finish some extra testing. So the ambiguity around if the project is complete and pointing to the lack of a release mirrors internal sentiment as well.
I had a funny thought that Bun might add a release tag while I was still writing the article. In that case I'd still publish it, because the point is we still don't know the cost it took to get to a viable, wide, release. The $165k isn't the full story.
It's not your article, bud. They have already addressed your concerns, and don't need to make changes just because you feel the article isn't "fair".
> My instinct on reading the article this morning was "this person doesn't know that Claude Code runs on Bun, which weakens their credibility in presenting the argument they are making here."
And your instinct was clearly mistaken. You should read the article more carefully before offering criticism.
There's an easy fix. If they don't want to take my advice that's completely fine.