facebook/folly

Choose this fork only if you need its exact historical snapshot or its local patches; for most adopters, upstream folly is the safer and more maintainable base.

Prefer this fork only if you need its older, customized behavior and are willing to own long-term maintenance. For most adopters, upstream folly is the better choice because this fork is materially behind and substantially diverged.

Prefer upstream unless you specifically need this branch's legacy behavior or downstream customizations. This fork is not a good choice for teams that want current support, low maintenance, or close alignment with Folly's ongoing development.

Choose this fork only if you need its older baseline and local tweaks; for most adopters, upstream Folly is the better default because this fork is materially stale and heavily diverged.

Choose this fork only if you need its older, customized Folly behavior and can accept long-term maintenance debt. If you want an actively maintained dependency, upstream is the safer default.

Prefer upstream unless you are locked to this fork's legacy patches. This fork looks like a stale, heavily diverged snapshot with meaningful local customization, but it is far behind current folly and likely missing many newer fixes and build/platform improvements.

Prefer this fork only if you specifically want its custom local changes and can accept a frozen, highly diverged Folly base. For most adopters, upstream is the better choice because this fork is stale and likely missing many newer fixes and features.

Prefer this fork only if you specifically need its older local patches and are willing to own the maintenance burden. For most adopters, upstream is the better choice because this fork is materially stale and diverged.