Hi everyone,

Thank you all for the great discussion. I played with the other GUIs
mentioned in the thread and very much like gitkracken (puns aside). It
seems to have a nice balance between an intuitive interface, a reasonably
close representation of the CLI, and an agnostic backend.

To provide a bit of context, Ivan's qualifiers are actually quite on point
for my use case. I will be teaching a group of scientists who have limited
exposure to version control (some use SVN sparingly), and very little if
any exposure to the command line. They normally work in IDEs (have moved
away from excel) in non-*nix envrionments. However, they recognize a number
of the benefits of using version control, especially with a github
web-interface, which is becoming more and more common in the energy/climate
science and policy community.

I think in this case (perhaps it is more special/unique than others,
perhaps not), I hypothesize that the marginal benefit of long-term adoption
is higher for this particular group using a GUI than it would be for a CLI.
Perhaps there is an interesting empirical study in here somewhere..

Cheers,
Matt




On Tue, Sep 6, 2016 at 4:46 PM, Schneider, Juliane <[email protected]>
wrote:

> Oscar never had to use Git!
>
>
>
> Juliane.
>
>
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows 10
>
>
>
> *From: *P Lijnzaad <[email protected]>
> *Sent: *Tuesday, September 6, 2016 8:35 AM
> *To: *Bennet Fauber <[email protected]>
> *Cc: *Software Carpentry Discussion <[email protected]>
> *Subject: *Re: [Discuss] Teaching Git with Github Desktop
>
>
> I concur with Juan Nunez-Iglesias, the git command line interface is
> horrendously complicated (or should I say inconsistent *), even for
> experienced programmers. This is of course partly due to the git data
> model, which is also very complicated (with >= 5 places to mentally keep
> track of things: working copy, index, repository, remotes, and stash). I
> had good experiences with Easy Git (eg; see https://people.gnome.org/~
> newren/eg/) when transitioning from svn. But it is aimed at exactly that
> (svn -> git), and I'm not sure it's maintained anymore. To further the goal
> of reproduceable research, anything that makes it easier to use git should
> be welcomed.
>
> (*) of course,  *Consistency is the last refuge of the unimaginative*
> (Oscar Wilde), but still ...
>
> Philip
>
> ​
>
> _______________________________________________
> Discuss mailing list
> [email protected]
> http://lists.software-carpentry.org/listinfo/discuss
>
>
_______________________________________________
Discuss mailing list
[email protected]
http://lists.software-carpentry.org/listinfo/discuss

Reply via email to