My argument is that what is an acceptable level of effort, or what the perceived I in ROI is, is very much dependent upon the individual. Unless it's a big button that says "push me", you'll always have someone displeased.
I don't find git challenging; many, many others don't either. The open source world has largely embraced git, and in doing so brought in a lot who would rather complain than act by either learning it or fixing it.
My argument is that what is an acceptable level of effort, or what the perceived I in ROI is, is very much dependent upon the individual.
I agree. Many people overestimate the Investment part. But I also think many people underestimate the Return part.
I don't find git challenging; many, many others don't either.
Challenging wouldn't be my word either. I'd say… annoying. I tried Darcs first, and Git seemed rougher. More things to remember, more involved work-flow. See the index for instance. I see little reasons for it. Some people love it, but now I have to keep 3 things in my head: working copy, index, and repository. I also don't like the git add && git commit dance (I know, there's a shortcut —one more thing to learn).
Then, as the OP pointed out, there's the command line itself. It's great for automation (just whip up a Bash script), but not so great for interaction. Git developed a number of commands solely for the purpose of interacting with it in the command line, like git stash, and of course many shortcuts. Yet more things to learn, for a suboptimal result.
A GUI would be better at some forms of interactions: branching, merging, amending patches, rebase, cherry picking, visualizing the history… So let's leave all that to the GUI, and let the command line do what it does best: automation, and programming API.
The way I see it, Git should comprise two parts:
A number of relatively basic command line utilities, designed as an API.
A GUI built on top of the API
Basic users would only use the GUI. And if you want something fancy (like automation), the API is there to make scripts.
I exist within the command line. My IDEs are all text-mode IDEs. The command line is the revered REPL so common in other languages such as Lisp, Python, JavaScript, and so forth. To claim that the command line is useful only for scripting ignores the interactive utility, e.g. REPL.
A story: I had a number of run ins with my university enrollment office that involved me directly sitting with the enrollment officer as she managed my class schedule. Her interface was telnet into a mainframe which presented a full curses-based text UI. She was a wizard at this UI, gliding from one frame to another, quickly filling out the forms and accomplishing her work.
Then one year the university felt that this system was too old and her system would be upgraded to a Windows GUI interface. That year I went to her again to schedule my classes. She double clicked to bring up the software and waited 30 seconds for it to load. Then she had to manually click on each field, each button, and a series of back buttons to return to the menu when she was done with a page.
I asked her how she felt about the new system? She said it is nice that someone else could quickly learn (there was no-one else, this was her job), but it was taking 3 times as long to accomplish the same task. She also lamented the fact that after me she had 2000 more students to enter into the system; a task that would now take three times as long.
What I got out of this is that newer isn't better, a GUI doesn't necessarily make for a better user interface. You have to look at the problem, the users, and how they interplay before you can understand what is wrong and how to fix it.
If you take me out of my command line, text-mode workflow and force a GUI into the mix, you'll make it hard for me to adopt it into my work. You'll also restrict my ability to simply shell into a remote machine and perform work.
You're comparing a good CLI with a crappy GUI. Also, did you say curses based? You can get quite graphic with those.
Of course the REPL thing is good. But it's not as good as it can be: you type a question, you get an answer back… It's a very tight loop, but there's still a delay. And the feedback is generally textual. Text is good, but sometimes, a picture is worth a thousand words. Also, in some systems, like Smaltalk, you can interact with the objects while they are running. That tends to get you the niceness of graphical interaction with the tight interaction of a REPL.
Then the CLI is text only. A GUI can be text and graphics. Of course, if you lose the text, and revert to "point and grunt", you are going to lose much. But a GUI doesn't have to be like that. We can do better.
I recall another comment praising the power of the command line, but his usage looks eminently graphical. He was doing 3D stuff with Maya. As a Linux Wiz, he shunned the Windows GUI and went like this:
A transparent terminal, fullscreen, in the foreground
Maya, fullscreen, in the background.
He configured his Maya instance to hide every GUI element, leaving only the 3D object he was working with. He then used the terminal to interact with Maya.
Now, what do you think is that? CLI? GUI? All I see is a freakishly good idea that we could use for a Git GUI. Drag and drop is cool, but the really important stuff is the instant, rich, graphical feedback. Do a merge, amend, rebase, commit, whatever, and see your commit tree change without having to type git log. The exact way one does stuff (point and grunt vs type commands) is probably less important than the way one sees stuff.
1
u/oursland Jun 20 '14
My argument is that what is an acceptable level of effort, or what the perceived I in ROI is, is very much dependent upon the individual. Unless it's a big button that says "push me", you'll always have someone displeased.
I don't find git challenging; many, many others don't either. The open source world has largely embraced git, and in doing so brought in a lot who would rather complain than act by either learning it or fixing it.