Thanks for the feedback!
One of the reasons RStudio is attractive is that the workshop becomes immersive and unified in one IDE. The git interface is pretty good, and merge conflicts are dealt with much as a standard text editor would, so standard but nothing as nice as Atom. For beginners, and intermediates, it appears sufficient. There hasnt been major drift across RStudio versions in a while, so even with a 6 month old version, it is fine (key being having RStudio > version 1.0). The RStudio interface also comes with a terminal built in. I'll check what it is for Windows, but that, I think, simplifies a lot of the issues with installing and using shell on Windows boxes, again simplifying the workflow. Still thinking aloud, but the more I think about this, the happier I'm getting :) On Wed, Mar 14, 2018, 10:31 AM Raniere Silva <rani...@rgaiacs.com> wrote: > Hi Abhijit, > > The Software Carpentry "bylaws" only mentioned that you must teach a > version control system. It could be Git, Mercurial, SVN or another one. > > In terms of learners experience during the lesson, I was helping on a web > development workshop and I noticed that different users had different > graphical user interfaces of GitHub Desktop client which made very hard to > help learners. I don't use R Studio's Git interface so I don't know how > often it change that will impact the workshop, for example, if one of the > learners installed R Studio 6 months ago and didn't updated it for the > workshop how much the graphical user interface will be different? Another > point, is how the conflict resolution works in R Studio? > > Cheers, > Raniere > >
_______________________________________________ Discuss mailing list Discuss@lists.software-carpentry.org http://lists.software-carpentry.org/listinfo/discuss
