Comment by simonw
2 days ago
If you're going to accuse someone of "an outright fabrication" it's on you to check that you're not wrong before you say that.
2 days ago
If you're going to accuse someone of "an outright fabrication" it's on you to check that you're not wrong before you say that.
I agree that ""an outright fabrication" is a bit too much.
But also the claims about the fuzzing in the original blog post are kinda too misleading. Fuzzing harness is basically just coverage-guided random bytes towards Bun's JS APIs and it will not really catch anything in depth from the code. Just the most obvious from the surface. And 24/7 fuzzing is introduced likely around the same time when Rust rewrite seemed to be main focus, as then the first issues were created. Current fuzzing does not give much trust about the code stability, but indeed the fuzzing has been started and likely improves in the future if someone puts some work for the harness.
> And 24/7 fuzzing is introduced likely around the same time when Rust rewrite seemed to be main focus,
This is false, it was done many months before (Nov 20 2025). There is some irony in your comment being in reply to a thread about verifying claims before posting them...
> This is false, it was done many months before (Nov 20 2025). There is some irony in your comment being in reply to a thread about verifying claims before posting them...
There is no evidence for this. It is integration PR to support fuzzing with one tool. The public repository does not have CI pipeline for it. Fuzzing is done privately somewhere, and the first linked issues are around April.