[andsoitis]

> in this fork

Not a fork, but a new project that takes a subset of the old Bun code to create something new, meant to complement Bun.

“Cruller is not intended to replace Bun for development. It is a minimal, specialized runtime for executing production code. In any case, I do not want to throw away such a large codebase that has taken several years to build. It makes more sense to turn it into a convenient embeddable library that can be used throughout the Zig ecosystem.”

[Aurornis]

That's a fork.

The git history should have been retained. It's helpful for the files that came over.

There is no good reason to erase all of the history. They should have deleted the files they didn't want to keep in a new commit.

[skeledrew]

A new project based primarily on existing code is still a fork. Also Ship of Theseus.

[otikik]

Wasn't the point of the Ship of Theseus precisely that establishing wether something is or isn't something else is at least complicated? Using it right after saying "X is still Y" kind of seems to make the opposite point.

[skeledrew]

The point here is that even though the water is murky about it's intrinsic identity, we know that it's still a particular ship with a particular back story, making at least it's extrinsic identity an immutable known. Fairly similar to how - most, if not all - complex living organisms continually gain and lose composing cells throughout their lives, yet their individual identities remain fixed: "I am X and this is my dog Y".

Similarly, a "fork" as we understand it in the context of software is this thing that, even though it's a modified copy, retains its extrinsic identity: "This software X was worked on in Y context, and is now being worked on in Z+ contexts". Same software, even if it gets a name change.