<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bun on Jiacai Liu's personal website</title><link>https://en.liujiacai.net/tags/bun/</link><description>Recent content in Bun on Jiacai Liu's personal website</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 16 May 2026 10:23:00 +0000</lastBuildDate><atom:link href="https://en.liujiacai.net/tags/bun/index.xml" rel="self" type="application/rss+xml"/><item><title>My Thoughts on Bun's Rust Rewrite</title><link>https://en.liujiacai.net/2026/05/16/bun-rust-port/</link><pubDate>Sat, 16 May 2026 11:59:54 +0800</pubDate><guid>https://en.liujiacai.net/2026/05/16/bun-rust-port/</guid><description>&lt;p&gt;
Before we discuss &lt;a href="https://github.com/oven-sh/bun/pull/30412"&gt;Rewrite Bun in Rust&lt;/a&gt;, there&amp;#39;s something that needs to be said, because no one is saying it.&lt;/p&gt;
&lt;p&gt;
Bun stands where it does today because of Zig.&lt;/p&gt;
&lt;p&gt;
&lt;figure&gt;
 
 &lt;img src="https://fs.liujiacai.net/cdn-img/zigcc/bun-rust-port.webp"
 
 
 /&gt;
 
&lt;/figure&gt;
&lt;/p&gt;
&lt;p&gt;
Jarred chose Zig back then not because it was &amp;#34;cool,&amp;#34; but because Zig enabled a small team to rapidly prototype a high-performance JS runtime without a GC, without a heavy runtime. Zig&amp;#39;s low friction, direct memory manipulation, and straightforward C interop were the core reasons Bun could punch above its weight on performance with an extremely small team in its early days. The architecture, data structures, and low-level design of Bun that you see today – that was shaped by Zig.&lt;/p&gt;</description></item></channel></rss>