According to the same stats, Linux and OS X usage is statistically tied at ~21%. If you take into account the fact that only about 2% of computer users run Linux at all it's pretty clear that programmers disproportionately prefer Linux (and to a lesser extent OS X) to other systems.
I personally have already moved away from github, but I still wish they would build some tools that work on Linux.
Video in action: https://www.youtube.com/watch?v=X4UQpGk1Ry8
Free download Win/Mac/Linux: https://secure.diffplug.com/versions/1.6.1
The rest of the product's docs are complete and full of screenshots:
https://docs.diffplug.com/1.6.1/ViewerDiffers/TextViewerDiff...
so the git client will be too. This client animates changes to the DAG, so I'm experimenting with animated gifs so that the manual can capture the feel of using it.
One criticism: that jgit tab needs a serious UX pass. It's extremely scary looking to someone who has never used it (me).
That being said, I'll be keeping a very close eye on your kickstarter. Very close.
The differ / merge resolution story is gonna get a whole lot better real soon.
> I think it's a myth that Linux users aren't interested in GUI tools.
It's definitely a myth, and a very dangerous and self-fulfilling one. I would strongly appreciate a GUI option for many common command-line tools. I like the command-line, and do most of my work there. But sometimes GUI tools are nice to have. The problem is that most GUI tools on Linux really suck, and most Linux tools don't even have a GUI at all[1]. Contrary to popular belief, it's not due to the inadequacy of GUI toolkits on Linux, but simply due to a lack of time actually spent developing these tools.
This ends up being self-fulfilling, because it raises the barrier to getting started on Linux, which keeps out people who would be otherwise very comfortable on Linux as an OS, but simply dislike being forced to use the command-line exclusively.
[0] Never bothered with dmenu, never really felt the need to set it up.
[1] I'm not counting ncurses-based interfaces as GUIs for these purposes.
Wow, that's exactly my case as well :). I could've written this, almost word for word (except I run debian on my servers, and archlinux on my laptop/home machines).
Personally I use a mac nowadays but still use and prefer the command line for this kind of thing. I tried using Github for Mac but quickly gave up the first time I had to do something vaguely complicated.
I guess I'm still a linux person at heart - you can tell if you prefer to 'brew install everything and have never actually used the App Store except to install Xcode :)
Regarding GUI, how do you initiate a pull request on the command line?
Aren't you taking this a little too personally? I mean, it's a software release for christs sake.
"GitHub Desktop is now available The new GitHub Desktop is now available"
And then I click on it to install it, I feel marginalized and hence a little insulted, when discovering I can't.
In this day, there are a great variety of cross-platform gui toolkits (e.g. https://en.wikipedia.org/wiki/List_of_platform-independent_G...), that could have been used. It is embarrassing for such a large organisation with all sorts of users using all sorts of machines to not release cross-platform tools. It if was just someone's personal project, or if it was a company's specialized toolkit for their specific customer base, the lack of cross-platform tools is excusable.
I feel you; I used to be a Linux desktop user and an advocate thereof. But that's the price that you pay for using the distant, distant third most-used OS for a company trying to drive user engagement with their product. You (the collective you) have to be an attractive market if you want commercial entities to consider you worth marketing to, y'know?
I mean git add, git commit, and git push/pull is 95% of what you'd do with git and it's not rocket science.
This seems strange. Did they not use Electron or Atom Shell or whatever it's called to build Github Desktop? If so, then is it not relatively trivial to create a GNU/Linux (or at least non-OSX-centric Unix) tarball of all the Javascript or whatever? If not so, then why not?
Regardless, my ultimate point is that Github went through all this trouble to make this Electron Shell thing and they don't even bother using their own tool. That seems surprising, Electron's merits and troubles aside.