(#uehjnbq) @abucci while I am glad it works for him, and he was points that are very valid, it doesn’t mean it will work for me. I am fine with git. But good for him! 😂

(#uehjnbq) @abucci I have to admit, coming from CVS, then Subversion (SVN) then Mercurial (hg) and finally Git (git), I actually kind of agree with some of the points there from the SQLIte author... -- That being said, I'm not switching from using Git anytime soon, as I've gotten so used to it. Maybe one day I'll write my own version control system 🤣 (kidding, or am? 🤔)

(#uehjnbq) @bender

(#uehjnbq) @ychbn but why?! Another version control to get used to, to learn. Git is so light, and so easy to setup. All you need is git, and SSH.

(#uehjnbq) @eaplmx First thing that I explored when was trying Fossil SCM for the first time is that it hasn't such thing as "staging area". All your changes are candidates to be commited by default.

(#uehjnbq) @bender yeah, it sounds interesting but I can't see myself switching from `git` anytime soon.

(#uehjnbq) @ychbn I'm seriously considering it for a next personal project, perhaps for classes too... Any general advice coming from git/gitbucket/github?

(#uehjnbq) @bender I really like its autosync feature.

(#uehjnbq) @prologic hmm, I started out on RCS and felt like CVS was a huge leap forward. I never used Mercurial. If I did switch version control systems I think I'd try pijul because the workflow sounds so much safer and easier than `git`. But I have to admit, the fact that the `fossil` executable is only around 4 Mbyes and contains the source control stuff, issue tracker, forum, chat room, user management, and ability to serve remote developers makes it pretty attractive. You need separate tools or plugins for that stuff with `git`and Microsoft bought one of them and another (Gitea) looks to be going down that road too.