FOSSIL: A complete Git alternative

I'm so fuckin tired of hearing x is user unfriendly, it's not intuitive enough.

Like fuckin yeah. Sometimes you have to actually learn something new to use something new when I first started driving it wasn't user friendly. I had to learn how to do it

I remember Linus saying in an interview that he'd only really been involved in git for the first 6 months or so and that the other devs had managed it without him since then. This makes sense - Linus's creations aren't successful because he's the only person who understands them, they're successful because there are so many other collaborators on them.

does he? i was under the impression that linus considers it just as stupid as everybody else and its existence is somewhat unsettlingly like a separate organism that lives in our collective brain activity..

No, you are not. People regularly equate Git and GitHub, though.

no, this is exactly what git does

Darcs came out in 2003—Git in 2005. It was novel at the time compared to the alternatives. Darcs started as alternative to CSV & Subversion, not Git. Unlike Git it works on patches, not snapshots which has advantanges in merge conflicts.

Am I missing something?

No and, in fact, this was (and still is) a selling point of Git over the alternatives (e.g. Subversion) available at the time that required you to "check out" some code and no one else could check out/modify that code while you had it checked out.

Since jujutsu is Git-compatible it has very much replaced Git for me and is what I'm using for everything now. Its workflow is so good and miles ahead of Git.

I was trying out Pijul for a while before that and while it has a lot of great ideas and has a lot of potential due to the way its foundations work its interface is way too janky right now and missing features and nothing I've reported or the many changes I've submitted have been fixed/pulled since March. I'd really like it to be good but alas...

I ‘forgot’ it on purpose.

The compatibility with Git means it is ultimately shackled to the design decisions fundamental to Git which require hacky workarounds. The maker of Pijul has pointed out some of the fundamental ways it can never handle patches is the manner of Darcs/Pijul, but I am not in the position to pull some of these quotes.

I would rather see revolution over evolution, & the weird ties to Google & hosting the project Microsoft GitHub rub me wrong.

Darcs is sort of like Pijul before Pijul. It is a little slower, but might not even affect you at your project size, but what it has instead is a longer history with more tooling & support—on the CLI, support from package managers, forge options. It ends up being my preferred option just for this reason even if Pijul has better performance, handles binary files, & the identity server is novel.

I think "Not Invented Here". Meaning he wants to build everything himself from scratch despite there being alternatives he can use instead.

E.g.: Building your own httprequest library rather than using the existing one which is good enough.

Not Invented Here, the urge to rebuild the wheel because someone else did it.

This - cathedral style development absolutely is a valid way to create free software and I don't believe Eric S. Raymond (the guy who, I believe, coined the term) claimed otherwise, only that the bazaar model was "better." Maintaining a bazaar style project is work, and it's work that easily leads to burnout. We should normalize the idea that you don't need to commit to being an "open source maintainer" to release a free software project; it should be enough to just release the source code (with or without binaries).

& The code behind Linux isn't ? People back then did some REAL sorcery with coding

Wow C, CSS and JS files at the same level. You don't see this every day

There are tabs above like a browser

Didn't like mixing issue tracking with vcs. I also didn't like any VCS hahaha, I was just writing shit in literally notepad

Why don't you tell me some more about what you like about Fossil... I'm assuming you've used other version control systems - how would you compare the feeling of actually using it in a collaborative workflow? How did you even come across Fossil in the first place?

This is my first time hearing about it, so would love to hear more straight from an actual user.

Rebasing is for advanced git users who knows what he's doing. If one does not know how to use it or not feeling comfortable in general, he can happily take his own code and try to merge it into the latest version instead. No one is judging.

For the rest of the world where projects are open-source, more often than not, not those projects inside a corporation where only the team lead is making decisions, it's a powerful tool to settle down conflicts sort out history.

One does not need to change the history again, if he's not comfortable with it. Just use git as if it's centralised VCS like SVN. No big deal. In fact, in corporations you do. There only needs to be one person who manages the repository.

I get why it exists, but yeah it's more trouble than it's worth in most cases.

How do you cleanly base your local changes against a new upstream version? Merges?

The binary executable for Fossil is a single file (repos are also single files, sqlite databases). That one executable does all the VCS functions but it also has a built-in web server that will host repos as a little customizable website. That's how you access the wiki, chat, forums, and ticketing system. You can also configure the repo, view timelines, view code, and all that stuff.

One can set up a proxy and publicly self-host the repo over the internet. That's what the official fossil site is, a hosted repo of it's own source code. I didn't feel like setting up a local web host, an ngnx reverse proxy, figuring out vpn for remote access, etc etc. So i just use synching and only run locally, because it's easier for me.

That's another nice thing about fossil, it's quite flexible and can grow with the needs of the project.