Re: Command-line git Vs IDE+plugin?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Nov 19, 2013 at 6:20 PM, Matthieu Moy
<Matthieu.Moy@xxxxxxxxxxxxxxx> 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.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]