3 ms·

It is true that Git can be used in a fairly simple way, although it is still significantly more complex than RCS. What's the point? RCS is not fit for distribu

It is true that Git can be used in a fairly simple way, although it is still significantly more complex than RCS. What's the point? RCS is not fit for distributed workflows/projects. Once you start to work in such a fashion, you want multiple remotes, tracking branches, rebasing (if only to make submitted patches as clean as possible), security/consistency per SHA hashes, etc. This simply implies more complexity and commands. Sure, git could be simpler, some argue that Mercurial is easier. But RCS is definitely not the program you want to compare git with.

NumberSix 12y ago
My point is the user interface, the command line interface, should be really simple, not much more than RCS's nine commands. Any necessary complexity should be hidden from the software developer so he or she can focus on developing the software and getting it working as quickly and effectively as possible. There are many examples of simple user interfaces layered on top of very complex programs and algorithms. Media players usually have a very simple GUI with a PLAY/STOP/PAUSE buttons and a volume control. Audio/video codecs, display drivers and so forth are extraordinarily complex but ideally the end user should not need to worry about this at all. Many of the Git GUI tools like sourcetree are an attempt to address this usability problem with the Git command line interface. Bit by Git