I like it for projects which may need to live a really long time between changes. Having a single .fossil file containing the entire project, it's history, docu

I like it for projects which may need to live a really long time between changes. Having a single .fossil file containing the entire project, it's history, documentation, and tickets in a set location makes it simple to pick something back up after x years. The optional web UI is simple HTML that is unlikely to break in future browsers. Finally, fossil is typically distribed as a single static binary, which makes it easy to install/update. If I was to have to build a VCS from source decades from now to get to my repo, I believe that fossil will be much simpler than git (which has a fair amount of build dependencies). Other commenters are talking about GitHub/Discord/Jira etc but I think that's missing the point a bit - in 20 years time are those closed sass services still going to exist? If they are, is your project still going to be there? And will you remember which flavour of the month sass you used for tickets?