# Bun from Zig to Rust

**URL:** <https://forum.freecodecamp.org/t/bun-from-zig-to-rust/794338>\
**Category:** Tech News Talk\
**Tags:** rust, zig\
**Created:** [July 14, 2026, 6:25pm UTC](https://forum.freecodecamp.org/t/bun-from-zig-to-rust/794338 "2026-07-14T18:25:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sky020](https://sea3.discourse-cdn.com/freecodecamp/user_avatar/forum.freecodecamp.org/sky020/32/128093_2.png) [@Sky020](https://forum.freecodecamp.org/u/Sky020)\
**Post date:** [July 14, 2026, 6:25pm UTC](https://forum.freecodecamp.org/t/bun-from-zig-to-rust/794338/1 "2026-07-14T18:25:12Z")

</div>

It might not be a secret I am interested in Rust. So, this was a tasty blog post to read:

> **[Rewriting Bun in Rust](https://bun.com/blog/bun-in-rust)**
>
> Why & how we rewrote Bun from Zig to Rust

The most interesting part I found was the [porting mistakes](https://bun.com/blog/bun-in-rust#porting-mistakes).

a. there are fewer than I would have expected  
b. many of these mistakes look eerily similar to the kind a human (_not me, of course_) would accidentally leave in

One major takeaway from this is summed in:

> …barely anyone noticed. Boring is good.  
> [Rewriting Bun in Rust | Bun Blog](https://bun.com/blog/bun-in-rust#production)

The rewrite is, and has been, used for a while now.

I think this is a useful read if you are interested in either Rust, or the current state of LLMs in programming.

If you do read it, consider sharing what most stood out to you.