I’ve tried Fossil a number of times, but several oddly-rigid aspects always manage to turn me off. Take, for example, the integrated bug tracker, which is novel and a big draw for me. Say I write up a bug and then notice an error in the description… I can’t edit it! I can merely append more comments, which also can't be edited or removed. The recommendation I found was that I should close (there's no delete!) the bug and create a new one. What’s the point of that level of immutability? I can tolerate the purity for the source code (e.g., the whole no rebase position they've taken), but for project metadata, I need way more freedom.<p>It’s a cool app that I’d love to use, but there are a few showstopper oddities.
It's been 10 years and I still need to look up the most basic things in git. It's just not intuitive to me at all.<p>Had fossil recommended to me. Also read their fossil vs git page, and I found myself agreeing with everything they said.<p><a href="https://fossil-scm.org/home/doc/trunk/www/fossil-v-git.wiki" rel="nofollow noreferrer">https://fossil-scm.org/home/doc/trunk/www/fossil-v-git.wiki</a>
It's always fascinating when someone building something yak shaves a project of major skill on the way. Both git and fossil would be notable on their own, but the respective authors simply needed a tool for Linux and Sqlite.<p>Really raises the boundary for what a software engineer can do. Very inspiring.<p>TeX was also built for TAOCP. Crazy stuff. Really makes me want to write code. Love it.
Related:<p><i>Why SQLite does not use Git (2018)</i> - <a href="https://news.ycombinator.com/item?id=36830813">https://news.ycombinator.com/item?id=36830813</a> - July 2023 (439 comments)<p><i>Why SQLite does not use Git (2018)</i> - <a href="https://news.ycombinator.com/item?id=29125934">https://news.ycombinator.com/item?id=29125934</a> - Nov 2021 (356 comments)<p><i>Why SQLite Does Not Use Git?</i> - <a href="https://news.ycombinator.com/item?id=26112802">https://news.ycombinator.com/item?id=26112802</a> - Feb 2021 (1 comment)<p><i>Why SQLite Does Not Use Git</i> - <a href="https://news.ycombinator.com/item?id=16806114">https://news.ycombinator.com/item?id=16806114</a> - April 2018 (608 comments)
People like to hate Git, but I guess that's because everyone uses it. I'm using Git, mostly with Idea UI, but sometimes with CLI and it's absolutely fine for me. I understand how Git works (the whole concept of commits, parents and so on), I follow some sane rules to prevent commit graph from turning to spaghetti and I never have any issues, it just works for me, 100% reliably.
I tried to use Fossil for personal projects but it didn’t work for me.<p>Idea is very appealing but in the end I found way too many distractions, especially in solo dev environment. I also agree that in group Git is standard so introducing something like Fossil might add needles friction.<p>But I still recommend checking it out. Some concepts are neat and might align with use cases that I don’t have.<p>Right now I’m experimenting with jj/jujutsu [1] and so far it works locally but I still hadn’t used the Git integration.<p>[1]: <a href="https://github.com/martinvonz/jj">https://github.com/martinvonz/jj</a>
I use Fossil every day for all my projects and it works great for me. Super easy to self host and has integrated Wiki, bug tracker, ticket system and a server. Very intuitive CLI too.<p>Highly recommended for indie/small teams.
> 2. A Few Reasons Why SQLite Does Not Use Git<p>It's fine if you don't want to use git, really.<p>But some of these objections don't make sense. Did you try "tig" and bare repos on a local machine/server?
How should other people look at us? We always have to change these core things. From proprietary source control to CVS - that was actually a good idea because it was the open source standard. Then we all changed again to SVN for reasons I can't remember and then to GIT. And indeed it is about time to change again.<p>For the others who have to earn the money to support these follies, it is all the same. We could as well have sticked to CVS.
I'd like to see Visual Studio able to use Fossil for its source control management rather than only really supporting Git. I suppose Microsoft owning Github is a major factor there, but it would be nice if there was at least an extension to do it. There's apparently one for VS Code.
It's a shame they don't use a SQLite database for version control. I know it's probably the least efficient way to store code changes but it would bring a whole new level to bootstrapping processes. Each code change would be inserted into the db by the code produced by the prior change.<p>It would be exciting as it is stable.