Remix.run Logo
pjmlp 3 hours ago

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

flohofwoe 2 hours ago | parent | next [-]

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

jonkoops 41 minutes ago | parent [-]

Same goes for io.js, which got so popular it actually got merged back into Node.js

well_ackshually 8 minutes ago | parent | prev | next [-]

Good thing there was no Bun community then.

kreco 39 minutes ago | parent | prev | next [-]

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.

TurdF3rguson 2 hours ago | parent | prev [-]

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.