Skip to main content

Github for Windows - first impressions

The other day I was listening to the recent Hanselminutes about Github for Windows (from now on abbreviated to GhfW), and decided to take it for a spin. I've had my pains explaining people how to set up Git on Windows, and I have pretty high hopes for this tool making it easier.

Dude, where's the frame..
At first I was a bit unsure if it was actually running, and not some popup on the current webpage:

Metro style lack of frame around the application
This is the first Metro style application I've installed, I think. And it didn't take long to like the feel of the application, cause it feels light, smooth and fast. I heard that GhfW can be a real memory hog, but I can't really confirm that here. It starts off taking 50 megs, and then later grows to 120 with a few repos checked out. At the end of writing this blog post it's at 200 megs.

But I already have Git set up
Now, my Windows is already set up to use Git, so I was a bit surprised to see that after logging in, I have to configure my full name and email. And GhW also automatically generates a new key which it authorizes at Github, even though I already have one set up. I guess that GhfW uses an isolated "We'll make everything just work (tm) for you" configuration somewhere, and I can see the reasoning for that.

It scans my homedir for repositories and prompts to import them, that's nice. Some of my local repos aren't hosted on Github, and it's nice to see that you can use GhfW for other repos as well, but I have no idea if my existing SSH-key authentication will work.

After importing some repos initially, I can't figure out how to import further repos. There's probably a button for it somewhere, but I can't find it.

Where are the buttons?
After playing around for a few minutes, this is a recurring thing for me in this modern Metro style interface:  I look around for a good few seconds before I find the button for what I want to do. It's just too unclear to me what is actually clickable, and what are just text or icons. Actually most text and icons are clickable, but my brain just doesn't cope with that yet.

A little later: Eureka! In order to import another repo, I have to drag it in from Explorer! I got that instruction by entering some text into the repository filter. See, that's what I mean.

FInally got a hint on how to import more repos
Some things can be right-clicked (repos, local changes), many cannot (commits). It takes a lot of clicking around to figure these things out.. Couldn't they build some conventions into the color scheme or something like that?

I wonder if the designers have done any usability tests on this..

Bugginess
I noticed a few bugs at first, like cryptic failure messages when pushing fails in mis-configured repos, and double-clicking below the list of repos will open the top one.

Then it got a bit nasty: I manage to land in a state where GhfW says the work tree is clean. Then it complains when I try to check out a branch, and shows me there are uncommitted changes (looks like there's some problems going on with line ending conversion there).

No local changes (background), but you have changes.
So I drop back to the command-line to fix up the repo, do a hard reset, then back into GhfW, just to see that it immediately has changes. And the changes do not match the git diff from the command-line. What the...

So, it could be that my installation is a bit messed up because of my existing .git settings or something like that, cause I don't think they would've shipped it everyone are having these problems.

The situation above occurred in a repo where I had worked with Windows line-endings checked in, and it could be that this conflicted a bit with how GhfW wanted to work things. They don't prompt you on how to handle line-endings during installation, so they must have some smart way of handling that, and maybe that failed in this situation.

Summary
I really like the rationale behind GhfW, which is making it super easy to get started with Git for Windows users. It certainly is easy to install, start new repos, and get them in and out of Github. And they also do install a Git command line, in case you want to go beyond the GUI.

The GUI is really nice, but it takes a bit of getting used to if you are new to Metro, I suppose.

For me, it feels a bit too buggy still, and a bit too alien that I could just recommend it to a complete Git newb, even if it was rock stable.

I suspect that they are aiming this product for a user group (I'm guessing suits in companies that buy Github's enterprise stuff) who will not be able to figure it out, and they need to do some usability testing here.

There are some more interesting notes on the design on Github's blog.

Comments

  1. We've tried to use this on the Enyo team but have been hitting some of the same problems involving phantom changes. I suspect that libgit just isn't baked enough on Windows. I like the idea, but it needs a lot of polish; for now, I'm sticking with TortoiseGit.

    ReplyDelete
  2. Thanks for the comment. Interesting that you see the same phantom changes.. Could you check if this might have something to do with line endings?

    Does this occur in repositories that you have checked out using GhfW, or were they already checked out using TortoiseGit (and if so, what was the core.autocrlf setting)?

    ReplyDelete

Post a Comment

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant

What I've Learned After a Month of Podcasting

So, it's been about a month since I launched   GitMinutes , and wow, it's been a fun ride. I have gotten a lot of feedback, and a lot more downloads/listeners than I had expected! Judging the numbers is hard, but a generous estimate is that somewhere around 2000-3000 have listened to the podcast, and about 500-1000 regularly download. Considering that only a percentage of my target audience actively listen to podcasts, these are some pretty good numbers. I've heard that 10% of the general population in the western world regularly listen to podcasts (probably a bit higher percentage among Git users), so I like to think I've reached a big chunk of the Git pros out there. GitMinutes has gathered 110 followers on Twitter, and 63, erm.. circlers on Google+, and it has received 117 +'es! And it's been flattr'ed twice :) Here are some of the things I learned during this last month: Conceptually.. Starting my own sandbox podcast for trying out everythin

Encrypting and Decrypting with Spring

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities . It "was decided" that we'd be doing AES with a key-length of 256 , and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet! The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE  in order to do 256 bits. It's a fascinating story , the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them. Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password

The academical approach

Oops, seems I to published this post prematurely by hitting some Blogger keyboard shortcut. I've been sitting for some minutes trying to figure out how to approach the JavaZone talk mentioned in my previous blog-post. Note that I have already submitted an abstract to the comittee, and that I won't publish the abstract here in the blog. Now of course the abstract is pretty detailed on what the talk is going to be about, but I've still got some elbow room on how to "implement" the talk. I will use this blog as a tool to get my aim right on how to present the talk, what examples to include, what the slides should look like, and how to make it most straightforward and understandable for the audience. Now in lack of having done any presentations at a larger conference before, I'm gonna dig into what I learned at the University, which wasn't very much, but they did teach me how to write a research paper, a skill which I will adapt into creating my talk: The one

Git Stash Blooper (Could not restore untracked files from stash)

The other day I accidentally did a git stash -a , which means it stashes *everything*, including ignored output files (target, build, classes, etc). Ooooops.. What I meant to do was git stash -u , meaning stash modifications plus untracked new files. Anyhows, I ended up with a big fat stash I couldn't get back out. Each time I tried, I got something like this: .../target/temp/dozer.jar already exists, no checkout .../target/temp/core.jar already exists, no checkout .../target/temp/joda-time.jar already exists, no checkout .../target/foo.war already exists, no checkout Could not restore untracked files from stash No matter how I tried checking out different revisions (like the one where I actually made the stash), or using --force, I got the same error. Now these were one of those "keep cool for a second, there's a git way to fix this"situation. I figured: A stash is basically a commit. If we look at my recent commits using   git log --graph --