<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>encoderer</author><text>I love git. I&amp;#x27;m a git power user. I&amp;#x27;ve used git as the datastore for a CRM I built.&lt;p&gt;But I respectfully disagree. Git is not &amp;quot;easy.&amp;quot; You&amp;#x27;ve been conditioned. You and I know that it&amp;#x27;s very very hard to lose work or lose commits with Git. I&amp;#x27;d say it&amp;#x27;s nearly impossible to do on accident. But in my first month with Git I rewrote several things because I messed up somehow and couldn&amp;#x27;t figure it out. I would hose my checkout and resort to doing a new clone. I&amp;#x27;ve since helped run a big transition from SVN to Git and saw the same struggles there.&lt;p&gt;Git is power tools for my code. I could never go back to SVN. But it&amp;#x27;s not easy.</text><parent_chain><item><author>npsimons</author><text>&lt;i&gt;It&amp;#x27;s actually a good idea. People often don&amp;#x27;t bother version-controlling simple stuff because it&amp;#x27;s a hassle.&lt;/i&gt;&lt;p&gt;Here&amp;#x27;s the thing that&amp;#x27;s funny to me: git is &lt;i&gt;easy&lt;/i&gt;. Everyone (especially mercurial users) goes on about how horrible the UI is, but when I think of git, I think of how similar it is to RCS: easy, quick, and simple. With both, I can diff things and check in changes &lt;i&gt;very&lt;/i&gt; quickly. I have a bunch of single files in RCS which I&amp;#x27;m moving over to git because it&amp;#x27;s a no brainer: all the speed and ease of use with a ton of advantages (such as dead simple replication) if I ever need them.</text></item><item><author>muyuu</author><text>It&amp;#x27;s actually a good idea. People often don&amp;#x27;t bother version-controlling simple stuff because it&amp;#x27;s a hassle.&lt;p&gt;I routinely use my own rdiff&amp;#x2F;rsync scripts but this is not something you find in every system and also not something most people would use.&lt;p&gt;A barebones, simple, no-install, easy, not-necessarily-for-experienced-developers VCS is a good thing to have.&lt;p&gt;BTW it&amp;#x27;s going at 1 release per day. Heh :-)</text></item><item><author>awalton</author><text>I think in a strange way, this tool is actually not a terrible idea. Git is not a configuration management tool, no matter how hard people try to shoe-horn it into that role. A simpler Git designed for configuration management is indeed a good idea.&lt;p&gt;Unfortunately, I think the implementation leaves a lot to be desired. For one, not including the committer is an important flaw. If you&amp;#x27;re only managing your own system&amp;#x27;s configuration, it makes sense, but surely ESR realizes that UNIX-based OSes are multiuser systems, often administrated by teams of people. Being able to track whodunnit is definitely an important part of the equation. (It&amp;#x27;d be incredibly clever if it signed the log with the user&amp;#x27;s public key too, but that might be asking a lot.)&lt;p&gt;Needing something like SRC to track changes to a simple README or HOWTO? My local bin dir? Ehh not so much. Especially if it&amp;#x27;s a software project? No, that definitely should live in the VCS with the code, so that those who touch the code will also touch the documentation. It says a lot about src that it doesn&amp;#x27;t even live in a src repository.</text></item></parent_chain></comment><story><title>Simple Revision Control</title><url>http://www.catb.org/~esr/src/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>IshKebab</author><text>Are you serious? Git is by far the least user-friendly version control system I&amp;#x27;ve used (Mercurial being the best).&lt;p&gt;Here are some longer articles explaining why git sucks so much (from a convenience &amp;#x2F; user friendliness point of view):&lt;p&gt;&lt;a href=&quot;http://reprog.wordpress.com/2010/05/10/git-is-a-harrier-jump-jet-and-not-in-a-good-way/&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;reprog.wordpress.com&amp;#x2F;2010&amp;#x2F;05&amp;#x2F;10&amp;#x2F;git-is-a-harrier-jump...&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;http://merrigrove.blogspot.co.uk/2014/02/why-heck-is-git-so-hard-places-model-ok.html&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;merrigrove.blogspot.co.uk&amp;#x2F;2014&amp;#x2F;02&amp;#x2F;why-heck-is-git-so-...&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;http://stevebennett.me/2012/02/24/10-things-i-hate-about-git/&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;stevebennett.me&amp;#x2F;2012&amp;#x2F;02&amp;#x2F;24&amp;#x2F;10-things-i-hate-about-git...&lt;/a&gt;&lt;p&gt;Version control is one of those annoying admin tasks that you have to do and what to think about as little as possible. Git makes you think about it &lt;i&gt;a lot&lt;/i&gt;.</text><parent_chain><item><author>npsimons</author><text>&lt;i&gt;It&amp;#x27;s actually a good idea. People often don&amp;#x27;t bother version-controlling simple stuff because it&amp;#x27;s a hassle.&lt;/i&gt;&lt;p&gt;Here&amp;#x27;s the thing that&amp;#x27;s funny to me: git is &lt;i&gt;easy&lt;/i&gt;. Everyone (especially mercurial users) goes on about how horrible the UI is, but when I think of git, I think of how similar it is to RCS: easy, quick, and simple. With both, I can diff things and check in changes &lt;i&gt;very&lt;/i&gt; quickly. I have a bunch of single files in RCS which I&amp;#x27;m moving over to git because it&amp;#x27;s a no brainer: all the speed and ease of use with a ton of advantages (such as dead simple replication) if I ever need them.</text></item><item><author>muyuu</author><text>It&amp;#x27;s actually a good idea. People often don&amp;#x27;t bother version-controlling simple stuff because it&amp;#x27;s a hassle.&lt;p&gt;I routinely use my own rdiff&amp;#x2F;rsync scripts but this is not something you find in every system and also not something most people would use.&lt;p&gt;A barebones, simple, no-install, easy, not-necessarily-for-experienced-developers VCS is a good thing to have.&lt;p&gt;BTW it&amp;#x27;s going at 1 release per day. Heh :-)</text></item><item><author>awalton</author><text>I think in a strange way, this tool is actually not a terrible idea. Git is not a configuration management tool, no matter how hard people try to shoe-horn it into that role. A simpler Git designed for configuration management is indeed a good idea.&lt;p&gt;Unfortunately, I think the implementation leaves a lot to be desired. For one, not including the committer is an important flaw. If you&amp;#x27;re only managing your own system&amp;#x27;s configuration, it makes sense, but surely ESR realizes that UNIX-based OSes are multiuser systems, often administrated by teams of people. Being able to track whodunnit is definitely an important part of the equation. (It&amp;#x27;d be incredibly clever if it signed the log with the user&amp;#x27;s public key too, but that might be asking a lot.)&lt;p&gt;Needing something like SRC to track changes to a simple README or HOWTO? My local bin dir? Ehh not so much. Especially if it&amp;#x27;s a software project? No, that definitely should live in the VCS with the code, so that those who touch the code will also touch the documentation. It says a lot about src that it doesn&amp;#x27;t even live in a src repository.</text></item></parent_chain></comment><story><title>Simple Revision Control</title><url>http://www.catb.org/~esr/src/</url></story>