> This post doesn’t make sense

The author's assumption is that a rewrite is not just a mechanical translation of code - it's also a state of stability. And no release, for the author (I agree) means no stability.

It's like a developer who says that after a week of work, a feature is 90% ready, but the other 10% is still not ready (for release) after months.

Author kept "going" in title because there has been no minor/major release in last two months which unusual for this project if you review the older releases.

bun in zig was used by many companies. some were using it in prod. how many of those are using it in prod? none, because bun in rust is not released yet.

Hence, the author concludes that rust rewrite is not complete as bun in rust is not released yet.

I agree with author's POV.

> Various people have claimed that Bun in Zig had a lot of tech debt. If they’re to be believed,

This is one of the funnier takes on the rewrite. Bun was held up as a flagship Zig project for years. Then they chose to rewrite in Rust and everyone up to the Zig author has suddenly switched to claiming that Bun was terrible code all along.

> Perhaps all this activity is paying down some of that debt.

Perhaps. But were that the case, one would think they'd be quite eager to say so.

tech dept is not a problem. to paraphrase captain Jack sparrow. "even if it were the most indepted working software project, IT WORKED". On the other side of the medal we have a rewritten software that although it's trumpeted for it's rewrite speed, it is not showing the same Release speed as the manualy written, "tech dept ridden" old one.