We sped up bun by 100x

Summary

Digest We rewrote git in zig and: Sped up bun by 100x Got 4x faster than git on an arm Macbook Compiled to WASM to be 5x smaller with 8.5x more exports Check out this demo to clone a repo in your browser! Rather than start with the theory behind the "swarming", we'll share how to code cannon yourself, describe how our zig rewrite of git went, and then dive into some of our theory behind why this works. How to code cannon yourself Install vers CLI First you'll need the vers CLI installed. $ curl -fsSL https://raw.githubusercontent.com/hdresearch/vers-cli/main/install.sh | sh After you've installed it, log in. $ vers login Now you have a working vers CLI ready to prepare your swarm infrastructure. Configure environment variables With the vers CLI you can define environment variables which get injected to all the VMs you create, making authentication for some CLIs a breeze. Here we'll walk through the environment variables we included for this project. First, create a new GitHub repository and then follow the instructions for creating a fine-grained personal access token. You'll want to create one that has Read and write access to content for the repository you're going to work on. github-token We configured it to have access to only the repos we're interested in code cannoning at for this project. Our rationale being we don't want one or multiple agents to get creative and start integrating other projects that aren't relevant. Once you have that API key then set it like so: $ vers env set GITHUB_API_KEY github_pat_... Next, from the vers dashboard click on the API Keys tab and create a new API key. After you've written it down someplace you won't lose it, you can set it to your environment variables (so an agent running in a VM would be able to on its own spawn further agents). $ vers env set VERS_API_KEY abc123... Finally, since we've been driving this using Claude, let's set an ANTHROPIC_API_KEY so any coding agent running in a VM works out of the box. $ vers env se...