Not that it's a particularly accurate stat, but:
replyhttps://github.com/oven-sh/bun/issues?q=is%3Aissue%20state%3...
119 open, 885 closed
https://github.com/denoland/deno/issues?q=is%3Aissue%20state...
10 open, 46 closed
You want a better source than the actual author of Bun?
replyAuthors can't exaggerate? Maybe some actual numbers can convince people.
replyHere: https://github.com/oven-sh/bun/issues?q=is%3Aissue%20%22Segm...
replyAround 2500 issues with segmentation fault.
As compared with 41 for deno
replyhttps://github.com/denoland/deno/issues?q=is%3Aissue%20%22Se...
With the total number of issues being 16,458 for bun and 14,259 for deno.
The cool thing is the author doesn't actually have to convince anyone
replyI believe the author is the creator of Bun.
replyIs he working for Anthropic now?
replyanthropic bought bun recently
replyFTA:
reply> why: I am so tired of worrying about & spending lots of time fixing memory leaks and crashes and stability issues. it would be so nice if the language provided more powerful tools for preventing these things.
Not a hard number obviously but a clear indication those issues exist.
I don’t understand: just use an agent to find all memory leaks and segfaults. I don’t get the argument if you are gonna vibe code anyway.
replyWith unlimited tokens make it a lint rule or auto formatter.
LLMs are a force multiplier, not magic. They benefit from good tooling.
replyIf you look at percent of segfault errors in each repo, Bun had a much larger percent. Although don't quote on me.
reply