As usual, most forks created out of community rupture eventually die.
I read it as "some forks are successful", and well, you need to fork to be a successful fork.
31–40 of 127 posts
As usual, most forks created out of community rupture eventually die.
I read it as "some forks are successful", and well, you need to fork to be a successful fork.
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.c…
As usual, most forks created out of community rupture eventually die.
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.
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
Does it work with WSL1? That’s all I care about.