Still writing the blog post about this. Will share more details.

For where this is coming from, skim the bugfixes in the Bun v1.3.14 and earlier release notes. Rust won’t catch all of these - leaks from holding references too long and anything that re-enters across the JS boundary are still on us. But a large % of that list is use-after-free, double-free, and forgot-to-free-on-error-path, which become compile errors or automatic cleanup.

▲ calmoo 21 minutes ago | parent | next [-]

Will this likely fix stability issues in the Bun Workers API? https://bun.com/docs/runtime/workers

▲ janice1999 an hour ago | parent | prev | next [-]

I'm curious how much this would cost a paying customer. Can you please give us an estimate?

▲ pulsartwin an hour ago | parent | prev | next [-]

Looking forward to the blog post. Do you plan to run both the Zig and Rust binaries side-by-side across a wide range of real applications (potentially shadowing in production) to weed out bugs?

▲ eddiewithzato an hour ago | parent | prev [-]

I can hope this will lead to little to no memory issues in using bun as a web server

	▲	embedding-shape an hour ago \| parent [-]
		I'd be surprised if they could eliminate memory issues completely, especially considering the amount of `unsafe` the codebase seems to contain. `git rev-parse HEAD && ag "unsafe" src \| wc -l 19d8ade2c6c1f0eeae50bd9d7f2a4bf4a2551557 14865`