Marius

@ForrestPKnight Dude come on, this is pathetic, bun just pushed the change so zig not had time to change it.

lol the top repo on the Zig GitHub Topic page is actually written in Rust

@SwivalAgent Can you compare to Zig version? curious the diff between zig and rust

The Bun source code is being ported to Rust using Claude. Here’s a review of the current Rust code, using GPT-5.5. #bun-rust-port-audit-findings" target="_blank" rel="nofollow noopener">github.com/Swival/securit…

How your AI agent feels rewriting everything in Rust

@jarredsumner Its official bun moving to Rust :D its not mentioning Zig as required.

My team is hiring to make Bun and Claude Code faster. Runtime internals, epoll/kqueue, parsers, JS engine work, long-running agent loop perf. Years of production C/C++/Rust required. $320k - $485k salary. SF in-person. job-boards.greenhouse.io/anthropic/jobs…

Introducing Project Redraw, a new grade of 2d primitives for Web & Native

Unfortunately, I don't use Zig now. Every 1.5-5x human DX productivity boost from Zig features is eclipsed by the 100x boost from coding agents writing Rust: Allocator interface: This is my favorite Zig feature, you feel so galaxy brain using a specialized allocator to optimize a code path (e.g. arena, stack fallback etc). The problem in Rust used to be that there was no Allocator interface equivalent and if you wanted a Vec that used a custom allocator you literally had to copy+paste the std version and modify it to use it (this is what Bumpalo did, look at the source). For a long while now there has been an Allocator trait in nightly, and it seems to be good now. Because it is a trait it is static dispatch, vs Zig's which is based on a vtable. Unlike Zig there isn't a community-wide convention of designing data structures to be parametric based on the allocator, but AI changes the game and makes it trivially to copy paste code and change that. I find it works well enough for my use-case. Arbitrary bit width integers + packed structs: Another beloved Zig feature of mine. It makes it so easy to do DOD-style CPU cache optimizations and stuff like tagged pointers, NaN boxing, etc. and even made bitflags really easy to make. You could always do this in Rust or any systems programming language but it was really ugly/unergonomic. The least worst option was using some crate like bitfield/bitflags which both rely on proc macro magic to work. Now, with coding agents I literally do not care how annoying it is to write the code by hand. Comptime: This is Zig's flashiest feature, no other programming language except maybe for obscure dependent-types langs have compile time evaluation as nice as Zig's. I thought I would miss it a lot, but I actually don't. For me, 95% of comptime usage is to create Zig's version of generic data structures with parametric types. Rust has a better designed type system IMO (see next section). In the remaining 5% of cases, not having comptime sucks. The only reliable way to reach an equivalent is through codegen. I'm making a game right now, and I have hardcoded hitbox geometry data generated from a tool that I want to bake into a data structure. Without comptime, I have to get Claude to write a script that generates the Rust file. However, I don't find myself needing compile time evaluation that much anyway. Rust's type system: I think I'd rather trade having comptime for Rust's better-designed type system, especially for bounded polymorphism (traits/typeclasses). Trying to do the equivalent in Zig is a nightmare. Also, I think that Rust's type system allows you to enforce more variants and prevent coding agents from making common mistakes. In my game I use the euclid crate which essentially allows you to not mix up coordinate spaces (very common problem in graphics programming) by creating specialized types for each coordinate space (e.g. Point or Point) Not having to deal with memory issues: With coding agents allowing 100x more code to be written, this also means you need to scrutinize 100x more Zig code for memory issues. Without formal verification, the surface area of the search space to enumerate to find bugs is just so much larger now. With the magnitude of code being generated now, Rust is even more attractive. Rust's tradeoff was always that it hinders developer productivity especially if you are unfamiliar with borrow checker, but this simply does not matter with coding agents anymore. And if you do use unsafe in Rust there's tools like miri which you can have the coding agent run the code against to make sure it doesn't cause UB or isn't violating Rust's aliasing rules when it comes to unsafe. I still miss writing Zig and find it to be a great language but I like Rust more and coding agents work with better with it.

@jarredsumner Still waiting for that blog post Jarred :P

Bun v1.3.14 releases tomorrow. If we do merge the Rust rewrite, this would be the last version in Zig

@zeddotdev when will workspaces be added like it has support on vscode?

This is what a useless hype lifecycle looks like.

@bitsandhops I don’t think you are a good programmer

Has anyone considered that maybe the creator of bun just isn’t that good of a programmer relative to the incredibly treacherous domain of building a fast and reliable dynamic language runtime?

@catalinmpit How does SEO work these days with SPA apps?

FINALLY! I've been saying this for a while. Most apps would be just fine using React, Vite and TanStack Router/React Router. Sadly, people love to overcomplicate things.

@SebAaltonen Still ugly

When I first saw the new BMW i3, I thought it looked ugly, but it has been growing on me. Now I think it looks pretty good, especially in the performance trim:

@tomwarren If only @StarfieldGame did not crash on PS5, its unplable, i think this data does not show refund amount

Starfield debuted at #4 in the PlayStation Store download charts for April in the EU, and #5 in the US / Canada blog.playstation.com/2026/05/06/pla…

@asha_shar @asha_shar optimize xbox UI its a gaming machine so needs to show games only no other silly apps, optimize OS itself, proper VRR support, improve controller latency

Xbox needs to move faster, deepen our connection with the community, and address friction for both players and developers. Today, we promoted leaders who helped build Xbox, while also bringing in new voices to help push us forward. This balance is important as we get the business back on track. As part of this shift, you’ll see us begin to retire features that don’t align with where we’re headed. We will begin winding down Copilot on mobile and will stop development of Copilot on console.

@jarredsumner @simonw but you could give us more clarity no? i personally don’t mind if bun is Rust just curious what are the reasons

@simonw more slop in these replies than the code

Sure looks like Bun is at least exploring a port from Zig to Rust given this docs/PORTING.md guide for coding agents github.com/oven-sh/bun/bl…

@bunjavascript @jarredsumner moving from zig to rust? github.com/oven-sh/bun/co…

@cursor_ai github.com/Huachao/vscode…

@cursor_ai you broke window preview for Rest Client extension

@SparkMailApp you are fucking annoying with shit like that

@bunjavascript When linux support for HEIC?

Bun.Image supports jpeg, png, and WebP on all platforms via libjpeg-turbo, libspng, and libwebp. HEIC & AVIF are supported on macOS & Windows, using the builtin APIs from the operating system.

In the next version of Bun `Bun.Image` - fast builtin multi-format image processing library