News for hackers. Stuff that matters.
Re:Cruller: Bun's Zig Runtime, Continued on Zig 0.16 by pjmlp on Thursday July 23, 2026 @03:46AM (#49018160)
As usual, most forks created out of community rupture eventually die.
Re:Cruller: Bun's Zig Runtime, Continued on Zig 0.16 by flohofwoe on Thursday July 23, 2026 @04:48AM (#49018626)
I think there are quite a few high profile examples where the fork was successful (egcs comes to mind which eventually became the official gcc, also all the BSD flavours). And even when the fork ultimately isn't successful, it sometimes at least forces the original project to adapt (e.g. ffmpeg vs libav).

E.g. "it's difficult to make predicitions, especially about the future" ;)

PS: of course for this specific project I don't quite understand the reason. The original Bun was largely a line-by-line port of esbuild from Go to Zig, so it's not like the original codebase was a marvel of engineering to begin with...

Re:Cruller: Bun's Zig Runtime, Continued on Zig 0.16 by jonkoops on Thursday July 23, 2026 @06:15AM (#49019283)
Same goes for io.js, which got so popular it actually got merged back into Node.js
Re:Cruller: Bun's Zig Runtime, Continued on Zig 0.16 by loeg on Thursday July 23, 2026 @10:05AM (#49021826)
egcs was almost 30 years ago, fwiw.
Re:Cruller: Bun's Zig Runtime, Continued on Zig 0.16 by flohofwoe on Thursday July 23, 2026 @11:05AM (#49022836)
...strange, I remember the drama like it was just yesterday ;)

But anyway, GCC was already an established and popular compiler at that time.

Re:Cruller: Bun's Zig Runtime, Continued on Zig 0.16 by TurdF3rguson on Thursday July 23, 2026 @05:18AM (#49018872)
I don't know that there's ever been a high-profile fork of a product acquired by such a fat, mealy, and genuinely unspooling parent as Anthropic's acquisition of Bun before.

But by all means I would love to hear some examples of that.

Re:Cruller: Bun's Zig Runtime, Continued on Zig 0.16 by kreco on Thursday July 23, 2026 @06:18AM (#49019305)
What is the point of the comment?

I read it as "some forks are successful", and well, you need to fork to be a successful fork.

Re:Cruller: Bun's Zig Runtime, Continued on Zig 0.16 by well_ackshually on Thursday July 23, 2026 @06:48AM (#49019498)
Good thing there was no Bun community then.
Re:Cruller: Bun's Zig Runtime, Continued on Zig 0.16 by fishgoesblub on Thursday July 23, 2026 @08:43AM (#49020683)
Valkey is going strong still. So is Jellyfin, and Gitea/Forgejo.
Re:Cruller: Bun's Zig Runtime, Continued on Zig 0.16 by allthetime on Thursday July 23, 2026 @11:37AM (#49023326)
Valkey made me forget redis existed in about a day. If I say redis now I actually mean valkey.
Re:Cruller: Bun's Zig Runtime, Continued on Zig 0.16 by jadbox on Thursday July 23, 2026 @12:10PM (#49023965)
Why is valkey better?
Re:Cruller: Bun's Zig Runtime, Continued on Zig 0.16 by allthetime on Thursday July 23, 2026 @12:33PM (#49024356)
They aren’t trying to sell me anything. Better multi-threading, better memory usage, open source, open governance. Redis went corporate.
Re:Cruller: Bun's Zig Runtime, Continued on Zig 0.16 by dnautics on Thursday July 23, 2026 @11:09AM (#49022894)
mariadb
Re:Cruller: Bun's Zig Runtime, Continued on Zig 0.16 by hiccuphippo on Thursday July 23, 2026 @11:17PM (#49030868)
MariaDB feels more like the original devs sold the brand and kept business as usual with a new name, not a community fork.