← Back to context

Comment by znkr

20 hours ago

> If a project in an unsafe language has ever had a memory bug (I'm looking at you, Bun), the maintainers objectively have a track record of not being capable of manual memory management. You wouldn't put a person who has a track record of crashing busses at the wheel of a school bus.

If you’re serious, you should stop using Rust (which happens to contain an unsafe language): https://github.com/rust-lang/rust/issues/44800

Just compare the Buns and Deno issue trackers.

Bun is segfaults galore, I’ve stumbled upon them.

In Deno they essentially only come from integrating with C and C++ libraries.

Hmm... A bug report from near a decade ago, where the bug was fixed within days. Not sure what your point is. If anything, it shows how much Rust cares about memory safety, because elsewhere it wouldn't be a compiler bug in the first place.

  • > Not sure what your point is

    I’m not the previous poster but it seems pretty clear the point is to show how silly that absolutist pronouncement is.

    • Being so absolutist is silly but their counter argument is very weak. Can I invalidate any memory safe language by dredging up old bug reports? Java had a bug once I guess it's over, everyone back to C. The argument is so thin it's hard to tell what they're trying to say.

      It's just as reductive as the person they're replying to.

      4 replies →