5 ms·

> Bun has had an extremely high amount of crashes/memory bugs Any stats/source? Not that I think it's false > and the ugly parts look uglier (unsafe) which en

by mi_lk 5mo ago

> Bun has had an extremely high amount of crashes/memory bugs Any stats/source? Not that I think it's false > and the ugly parts look uglier (unsafe) which encourages refactoring. Looks like Bun owes that to itself to some extent, not solely because of the language

enricozb 5mo ago
I believe the author is the creator of Bun.
- brazukadev 5mo ago
  Is he working for Anthropic now?
  - danaw 5mo ago
    anthropic bought bun recently
    - brazukadev 5mo ago
      That's exactly my point. The fact they created Bun does not mean they will do what's better for Bun and the people using it.
Ygg2 5mo ago
If you look at percent of segfault errors in each repo, Bun had a much larger percent. Although don't quote on me.
afavour 5mo ago
FTA: > 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.
- qudat 5mo ago
  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. With unlimited tokens make it a lint rule or auto formatter.
  - duggan 5mo ago
    LLMs are a force multiplier, not magic. They benefit from good tooling.
    - qudat 5mo ago
      Literally the model “mythos” is being marketed towards finding these exact type of bugs used for exploitation. I really don’t understand the argument: are agents not good at findings memory management issues? What’s the gap?
dmd 5mo ago
You want a better source than the actual author of Bun?
- nesarkvechnep 5mo ago
  Authors can't exaggerate? Maybe some actual numbers can convince people.
  - frde_me 5mo ago
    The cool thing is the author doesn't actually have to convince anyone
  - nicce 5mo ago
    Here: https://github.com/oven-sh/bun/issues?q=is%3Aissue%20%22Segmentation%20fault%22 https://github.com/oven-sh/bun/issues?q=is%3Aissue%20%22Segm... Around 2500 issues with segmentation fault.
    - shpx 5mo ago
      As compared with 41 for deno https://github.com/denoland/deno/issues?q=is%3Aissue%20%22Segmentation%20fault%22 https://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.
dminik 5mo ago
Not that it's a particularly accurate stat, but: https://github.com/oven-sh/bun/issues?q=is%3Aissue%20state%3Aopen%20segfault https://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%3Aopen%20segfault https://github.com/denoland/deno/issues?q=is%3Aissue%20state... 10 open, 46 closed

by mi_lk 5mo ago

enricozb 5mo ago

I believe the author is the creator of Bun.

brazukadev 5mo ago
Is he working for Anthropic now?
- danaw 5mo ago
  anthropic bought bun recently
  - brazukadev 5mo ago
    That's exactly my point. The fact they created Bun does not mean they will do what's better for Bun and the people using it.

Ygg2 5mo ago

If you look at percent of segfault errors in each repo, Bun had a much larger percent. Although don't quote on me.

afavour 5mo ago

FTA: > 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.

qudat 5mo ago
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. With unlimited tokens make it a lint rule or auto formatter.
- duggan 5mo ago
  LLMs are a force multiplier, not magic. They benefit from good tooling.
  - qudat 5mo ago
    Literally the model “mythos” is being marketed towards finding these exact type of bugs used for exploitation. I really don’t understand the argument: are agents not good at findings memory management issues? What’s the gap?

dmd 5mo ago

You want a better source than the actual author of Bun?

nesarkvechnep 5mo ago
Authors can't exaggerate? Maybe some actual numbers can convince people.
- frde_me 5mo ago
  The cool thing is the author doesn't actually have to convince anyone
- nicce 5mo ago
  Here: https://github.com/oven-sh/bun/issues?q=is%3Aissue%20%22Segmentation%20fault%22 https://github.com/oven-sh/bun/issues?q=is%3Aissue%20%22Segm... Around 2500 issues with segmentation fault.
  - shpx 5mo ago
    As compared with 41 for deno https://github.com/denoland/deno/issues?q=is%3Aissue%20%22Segmentation%20fault%22 https://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.

dminik 5mo ago

Not that it's a particularly accurate stat, but: https://github.com/oven-sh/bun/issues?q=is%3Aissue%20state%3Aopen%20segfault https://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%3Aopen%20segfault https://github.com/denoland/deno/issues?q=is%3Aissue%20state... 10 open, 46 closed