Cruller: Bun's Zig Runtime, Continued on Zig 0.16

holysantamaria

What makes Bun Bun is all the things that got removed from this project. Node is already powerful enough and well maintained. Why would anyone use this?

Copenjin

Heroic effort, sifting through that code I mean, but frankly I would have started a new one from scratch, the only thing of value is the name/popularity of the original project.

pjmlp

As usual, most forks created out of community rupture eventually die.

andai

There seems to be some confusion here (including in the linked discussion?) about what this is. This is not continuing the development on the original Bun (Zig) codebase. It is extracting a subset of that codebase for deployment purposes. The full version of Bun (presumably in Rust?) will continue to be used for actual development. So it is not a replacement for Bun, but a supplement to it. https://news.ycombinator.com/item?id=49018157

jdw64

But according to Andrew Kelly, Bun was full of bad Zig practices. So why did they keep pushing forward with Zig?

self_awareness

Oh no, it tastes like Andrew Kelleys problem again! Forking an "embarassing project" is really something. Edit: Huh? Downvote explanations are welcome. I wrote only what Andrew Kelley wrote.

djfobbz

Does it work with WSL1? That’s all I care about.

mekky16

i dont see the point of this to be honest, if rust is actually better for bun why are you people just hating on it for no reason? a software doesnt have to be written in your favourite language for it to work. bun was a sloppy project is zig and still sloppy in rust

Skywalker13

I don't understand why the git history has been pruned in this fork. According to the first commit in this fork: > Squashed as a single orphan commit — the original oven-sh/bun history isn't relevant to this stripped fork and its shallow clone doesn't push cleanly to a fresh remote. IMHO it's always a bad decision to do that. Here, all commit authors are lost. The original history is always relevant.

theawesomekhan

One thing to point out is all the author's comments seem LLM generated and so does the README and the latest commit to the branch (large explanation in a comment and then change)..

dbalatero

> My idea is to strip the system down as much as possible and leave only what is required for production. > Development would be done using the full Bun runtime, while production would use its lightweight fork, Cruller. I do not have the resources of the Oven team to develop and maintain a massive general-purpose runtime, so I want to focus on specific production requirements. I don't know about others, but I don't think I would deviate my development runtime from my production runtime so significantly. The chance for behavior that only rears its head in production is too high for my liking.

ksec

This got me thinking, What if you feed Bun's code into AI, and instead of Rewriting it in Rust, tell it to follow TigerStyle as much as possible?

bradhe

Nice this is going to be a fun project to watch for 2 weeks before everyone forgets about it!

up2isomorphism

The statement is weird, of course it is aiming at replacing bun, and it might not be a bad thing. Not sure what that clarification serves.