<story><title>Fossil SCM</title><url>https://www.fossil-scm.org/index.html/doc/trunk/www/index.wiki</url></story><parent_chain><item><author>bananaoomarang</author><text>This is a good point. I think once developers learn Git (or as much as they need to use), then they forget how esoteric the the cli tool is.&lt;p&gt;I think a lot of devs have the attitude that a tool being more difficult to use makes it a powerful one (cf. Vim&amp;#x2F;Emacs), whereas most people are happy when tool does the three things they need to get from a=&amp;gt;b, b=&amp;gt;c, a=&amp;gt;c.&lt;p&gt;Maybe this is to do with our desire for everything to be as flexible as the programming languages we write in. Most people don&amp;#x27;t view computers as blank slates ready to do their bidding, but as systems where the behaviour of a few facets is to be memorised without concerns for their mechanics or abstractions. This is probably one of the reasons that mobile software is seen as so easy to use, since it obscures&amp;#x2F;abstracts elements like the filesystem from the user.&lt;p&gt;Glad to hear Fossil is friendlier.&lt;p&gt;EDIT: I should say that I am a heavy user of Vim, Emacs, Git and Arch Linux, I am just saying that these tools often require a large up front investment, and this can be detrimental as well as sensible.</text></item><item><author>bachmeier</author><text>Here&amp;#x27;s my story. I wanted to use version control on my research projects, but asking my collaborators to use Git was too much. They were supposed to figure out a staging area and pushing and pulling and then they&amp;#x27;d get a bizarre error about a merge conflict. They&amp;#x27;d do a search and Stack Overflow told them to type in an incantation. The repo is messed up, the collaborator goes back to email, and I&amp;#x27;m left sorting through the rubble formerly known as a repo.&lt;p&gt;I switched to Fossil a few months ago. Nice website that holds all the information. fossil commit -m &amp;quot;Message&amp;quot; is all they need to know. If they forgot to pull, it stops and tells them to do so. They type fossil update and go on with their lives. Zero problems so far and a more productive workflow overall.</text></item></parent_chain><comment><author>throwawayish</author><text>&amp;gt;  This is a good point. I think once developers learn Git (or as much as they need to use), then they forget how esoteric the the cli tool is.&lt;p&gt;This is more up to git being horribly leaky about &lt;i&gt;all&lt;/i&gt; it&amp;#x27;s internal implementation details. I&amp;#x27;m not a git developer, and not even that great a user, but I know about trees and indices and refs and refspecs and packs and reachability and objects and merge drivers and smudge and clean and diamonds and countless other details that I feel should be encapsulated way better. git also has next to none documentation of these concepts.</text></comment>
<story><title>Fossil SCM</title><url>https://www.fossil-scm.org/index.html/doc/trunk/www/index.wiki</url></story><parent_chain><item><author>bananaoomarang</author><text>This is a good point. I think once developers learn Git (or as much as they need to use), then they forget how esoteric the the cli tool is.&lt;p&gt;I think a lot of devs have the attitude that a tool being more difficult to use makes it a powerful one (cf. Vim&amp;#x2F;Emacs), whereas most people are happy when tool does the three things they need to get from a=&amp;gt;b, b=&amp;gt;c, a=&amp;gt;c.&lt;p&gt;Maybe this is to do with our desire for everything to be as flexible as the programming languages we write in. Most people don&amp;#x27;t view computers as blank slates ready to do their bidding, but as systems where the behaviour of a few facets is to be memorised without concerns for their mechanics or abstractions. This is probably one of the reasons that mobile software is seen as so easy to use, since it obscures&amp;#x2F;abstracts elements like the filesystem from the user.&lt;p&gt;Glad to hear Fossil is friendlier.&lt;p&gt;EDIT: I should say that I am a heavy user of Vim, Emacs, Git and Arch Linux, I am just saying that these tools often require a large up front investment, and this can be detrimental as well as sensible.</text></item><item><author>bachmeier</author><text>Here&amp;#x27;s my story. I wanted to use version control on my research projects, but asking my collaborators to use Git was too much. They were supposed to figure out a staging area and pushing and pulling and then they&amp;#x27;d get a bizarre error about a merge conflict. They&amp;#x27;d do a search and Stack Overflow told them to type in an incantation. The repo is messed up, the collaborator goes back to email, and I&amp;#x27;m left sorting through the rubble formerly known as a repo.&lt;p&gt;I switched to Fossil a few months ago. Nice website that holds all the information. fossil commit -m &amp;quot;Message&amp;quot; is all they need to know. If they forgot to pull, it stops and tells them to do so. They type fossil update and go on with their lives. Zero problems so far and a more productive workflow overall.</text></item></parent_chain><comment><author>masklinn</author><text>&amp;gt; I think once developers learn Git (or as much as they need to use), then they forget how esoteric the the cli tool is.&lt;p&gt;Some of us never forget. And &amp;quot;esoteric&amp;quot; is way to kind a word for that thing, it is abstraction leak made software.</text></comment>