A killer-feature measure is not very useful way of selection, as it's not how projects select a VCS - many projects/teams have individual requirements which aff

A killer-feature measure is not very useful way of selection, as it's not how projects select a VCS - many projects/teams have individual requirements which affect such feature considerations. In my somewhat simplified view, Git's 'killer-feature' by now is simply its ubiquity. By the same token, for Fossil's this could be claimed as a single binary that does it all. Just download the binary, and you've got the ubiquitous set of project-related facilities: VCS/tickets/docs/wiki/team/forum/chat with simple aporoach to sync and self-host.