3 comments

  • DASD an hour ago

    First merge of this document was 2026-07-28 (new to me, at least, and maybe others).

      verdverm 44 minutes ago

      a bunch of those sound like things I do not want, mostly an opinionated list with a bunch of nothing burgers in there

      my first question is always, is it git compatible, because I have team members to support and we are not going to force them to switch

      for all the pains of git these alternatives proclaim, they come with their own, and I hardly ever hit the ones with git

        DASD 11 minutes ago

        I've been using Fossil(and Git) since about the same time(late 2000s), so I, don't harp on the idea of Fossil as an alternative. Skewed, but I can even see Git as an alternative to Fossil. The document was new to me though. As I admittedly age through the end of my corporate life, a significant reason for me to keep considering Fossil is the size of the team I expect to work with. More and more, my desire is to work on smaller projects and more of my own startup endeavors. Also, thankfully, I'm not terribly sensitive to Git compatibility. Many do not have this flexibility for considerations.

        A decade of SQLite use has also made me comfortable with the underpinnings along with a preference for the batteries-included functionality(.e.g wiki, issues, and notes). I'm also not beholden that something better might come along, say Jujutsu and even more so when it has its own native backend.