Re: Command-line git Vs IDE+plugin?
- From
Gauthier Östervall <gauthier@ostervall.se>
- Date
- Dec 4, 2013, 09:56 UTC
- Message-ID
- <CAM8gEgi1+4EYXAMzHxWbh0qZiFWGSU52fLKSeiPS-O3Uk5ifgw@mail.gmail.com>
- In-Reply-To
- <vpq1u2c9ukx.fsf@anie.imag.fr>
On Tue, Nov 19, 2013 at 6:20 PM, Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> wrote:
> One thing the command-line does well is to give names to concepts > (basically, command names, option names, ...). It's easy to write in a > tutorial or an email "run the command 'git foo'". It's less easy to > write "click on that red button, on the right of the green one".
And it is also easier for many to press a button than writing a command. This is a bad thing, in my experience. In a GUI, people tend to take chances: "Oh, reset, that sounds like what I want. What, it did not work? Oh there is this option 'hard', let's tick it and see what happens."
Another thing GUIs do not (often) offer is history. I would be lost if I couldn't see what I was trying to do 5 commands ago (before someone interrupted me), or refer to a previous error message.
But if you cannot touch-type, buttons are going to be more attractive.