Hacker News new | ask | show | jobs
by pjmlp 10 days ago
As usual, most forks created out of community rupture eventually die.
5 comments

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...

Same goes for io.js, which got so popular it actually got merged back into Node.js
egcs was almost 30 years ago, fwiw.
...strange, I remember the drama like it was just yesterday ;)

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

Valkey is going strong still. So is Jellyfin, and Gitea/Forgejo.
Valkey made me forget redis existed in about a day. If I say redis now I actually mean valkey.
Why is valkey better?
They aren’t trying to sell me anything. Better multi-threading, better memory usage, open source, open governance. Redis went corporate.
mariadb
MariaDB feels more like the original devs sold the brand and kept business as usual with a new name, not a community fork.
Good thing there was no Bun community then.
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.

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.