> Git command line interface isn't friendly to new users This is different from 'broken'. Broken implies that it does not do what it claims it will.
> because "git checkout" do too much for the same command > depending of what arguments the user pass. > Why do we can't have "git undo" that ony works with the working copy? > Why do we can't have "git recovery" that only works with old revisions? I think separating things we wish Git would do and how we teach Git is probably a good idea. Those are complaints about Git, but there it is. We should (and are) talking instead about how to teach it, warts and all. > As a intermediate user I understand why all the actions previous > mentioned are under "git checkout" but for a new user this isn't clear. Clarifying those things, if that's necessary, is one of the challenges. I'm not sure that hiding them from new users is a service. I think it would be in keeping with the SWC philosophy if we ask a second question along with whether using a GUI makes teaching GIT easier: Does teaching from the GUI prepare them well to learn enough on their own to become intermediate users? Since reproducibility is part of the SWC motivation, and quite a lot of reproducibility is driven from the command line, every time we move away from the command line and teach from the GUI, we move, in some sense, away from the tools needed to provide reproducibility. Teaching from a GUI may -- probably -- makes it easier to teach the specific tool, but perhaps it skimps on the glue that binds the tools together. I think we would do well not to focus on teaching each of the tools quite so intently that we lose sight of the overall purpose and intent of the SWC bootcamp. _______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/listinfo/discuss
