> > Fossil is a recent git alternative
> It’s almost as old as git. Fossil has been around since 2006, while git was born in 2005.
I'm assuming the author recently discovered fossil, but it is an absurd statement regardless :)
I've sort of wanted to use fossil for a real project of my own, but its own idea of workflows just... puts me off completely. I stick to Git. Git won the minds of developers not because it was first (by far, it wasn't), but because it's better than the rest.
Nah, it won because of GitHub.
Basically. I liked mercurial better than git, but GitHub's become the center of gravity for a lot of development.
It won well before GitHub. and I always liked it better than Mercurial too :)
That's just not true. SVN was more popular than git until several years after GitHub was founded. Mercurial was reasonably popular as well.
SVN may have been more widely used, but it was on the way out by the time GitHub was launched. It was the incumbent, at least in communities at the forefront of change. GitHub and integration with Microsoft tools certainly accelerated it's adoption into the enterprise environment, but among the "new VCSs with a future," git had already won.
? Github launched in 2008, git was popular then but not the completely dominant thing it is now.
Most big open source projects switched to git way before GitHub existed. It was already popular when they launched and that's the reason they succeeded.
Re:
by jesseduffield on Saturday August 05, 2023 @06:45PM
(#37016980)
Whoops! I should have fact-checked that: I had it in my head that it was recent based on there being so much recent discussion of it online. I've updated the post
It’s almost as old as git. Fossil has been around since 2006, while git was born in 2005.
> Merge conflicts aren’t first class
Another DVCS where conflicts are first class is Pijul. It also has a solid theoretical foundation, which it inherited (and expanded upon) from its predecessor, Darcs.