People frequently ask:
> How is Bun sustainable? If I bet my company’s tech stack on Bun, will Bun still be around in a few years?
We didn’t have a great answer to this question, until today
JavaScript was never designed for the server. If that doesn't change soon, JavaScript on the server will be replaced by Rust.
The fix needs to happen in the engine. Sound types. Ahead-of-time compilation. Threads with shared objects.
JavaScript has been through this before.
In 2011, Google set out to replace JavaScript with Dart, arguing JavaScript couldn't be fixed by evolving it. Then ES2015 shipped.
It's time to do that again.
JavaScript engines like JavaScriptCore and V8 have some of the best compiler tech in the world.
An open question: with sound types, ahead-of-time compilation for statically typed code, and JITs for everything else, can JavaScript be competitive with Rust and C?
Opus 5.5 is a very good model and I expect it will quickly become the daily driver for a lot of people.
The writing style is so much better. It writes like Opus 4.6 and codes like Fable 5.1.
Introducing Claude Opus 5.5, the first model in our new Claude 5.5 family.
It performs at the level of Claude Fable 5.1 for most tasks, and costs 40% less to run than Opus 5.
In the next version of Bun
`Bun.FetchSession` gives you a `fetch` function with its own keepalive connection pool
ALT Dark slide with the Bun logo and a "new in Bun" badge. Large headline: "Bun.FetchSession". Subtitle: "fetch() with its own connection pool." Below it, a code sample:
const api = new Bun.FetchSession({
proxy: "http://proxy:8080",
tls: { ca },
keepAlive: { idleTimeout: 30 },
});
await api.fetch(url);
new Octokit({
request: { fetch: api.fetch },
});
"api.fetch" is highlighted in both places. Three cards at the bottom read: "Own pool: isolated keep-alive", "Proxy + TLS: set once per session", "Drop-in: works in any SDK".
Claude Code's idle memory dropped 14% on Linux with Bun v1.4.1
ALT Line chart: "Claude Code — p90 idle memory usage (Linux)", headline "−14%, lower is better". Two lines plot 90th-percentile memory of idle Claude Code processes against process uptime, from about 1 hour to 2 days. The grey "Before" line rises from 490 MiB to 665 MiB; the orange "Bun v1.4.1" line stays below it the whole way, rising from 431 MiB to 572 MiB. Footnote: p90 RSS after 3+ min idle, Linux, Claude Code 2.1.260+ vs earlier versions, same days and session age, Sep 4–9, 2026; y-axis starts at 250 MiB.
Excited to see everyone tomorrow!
We’re at capacity with 130+ on the waitlist, so if you can’t make it please mark “can’t go” on Partiful so someone else can grab your spot
my favorite way to keep claude running overnight without /loop or /goal
tell claude something like:
“I’m going to sleep, and when I wake up I would love to see X result. Post frequent updates to <slack channel> as you make progress.”
Bun v1.4.1 is a big upgrade to Bun’s bundler.
On a 200-route React app over simulated 4G, navigating between routes is 38% faster than Bun v1.4.0, and 10% faster than Vite v8.2.2.
ALT Slide titled “Route navigation on 4G”, subtitle “click → lazy route’s chunks fetched, parsed, and rendered by React · lower is better”. Three horizontal bars: Bun 1.4.0, 1104 ms (dark gray); Vite 8, 757 ms (gray); Bun 1.4.1, 681 ms (pink-to-orange gradient, labeled −38%). Table below with columns Bun 1.4.0 / Vite 8 / Bun 1.4.1: Requests per navigation 108 / 108 / 61; LCP, cold first load 736 ms / 560 ms / 576 ms; JS chunks emitted 918 / 908 / 750; Total JS shipped (gzip) 1.75 MB / 1.67 MB / 1.61 MB. Footnote: 200 lazy routes, 800 components, 30 npm deps, React Compiler on in both, headless Chrome, 170 ms RTT / 9 Mbps, cold cache, median of 7 runs × 12 routes; Bun built with bun build –splitting –min-chunk-size=16384 –react-compiler; Vite 8.2 with @vitejs/plugin-react 6 compiler: true.
Merging 1 more memory usage reduction PR targeting long-running often idle servers & CLIs and then finishing release notes and then it will be Bun v1.4.1
In the next version of Claude Code
Claude Code starts 20% faster
ALT Claude Code keynote-style slide on black. Headline: “Time to input box is now 20% faster.” Two horizontal bars: 2.1.250 at 397 ms (gray), 2.1.252 at 318 ms (orange). Footer: Linux x64, quiet box, median of 25 interleaved launches.
This was a series of performance optimizations across Bun and JavaScriptCore that will benefit every app using bun build —compile, and not just Claude Code.