The architecture narrows the field. The everyday workflow decides whether a tool fits.
Small, movable references to commits and a staging area make it easy to shape changes before recording them. Teams often add a central review service by convention.
A distributed changeset model with a focused command line. Bookmarks act as movable labels; named branches are permanent history metadata.
A repository server assigns revisions to committed changes. Branches and tags are conventionally created as repository copies.
Version control packaged with a built-in web interface, wiki, and issue tracker. It keeps project artifacts together in a single repository file.
| If you value... | Look at... | Why |
|---|---|---|
| A large ecosystem and flexible branching | Git | Widely supported workflow and hosting choices. |
| A focused distributed command line | Mercurial | Explicit changesets and bookmark-based collaboration. |
| A single authoritative repository | Subversion | Server-centered history and access control. |
| Version control and project tools together | Fossil | Web UI, tickets, and wiki are part of the system. |
These are starting points, not performance rankings. Migration cost and team familiarity matter too.