Live data from Hacker News

GitHub for Mac

github.com

61–70 of 214 posts

Re: GitHub for Mac

#61
post #28

I hate all the visual clutter and unjustified complexity the new stylish iOS-like interfaces bring. Those interfaces are only good for Twitter and friends (and for screenshots). Some feedback: * Get rid of huge spacing everywhere (for example here: http://github-images.s3.amazonaws.com/blog/2011/mac-screensh... ) * Make animations go faster. * History should have preview pane with diffs (see Mail) instead of making m…

FWIW, I disagree that windows should freely proliferate. I prefer apps that stay in a single window.

Also, you should let some of that angst go, because it's clear that Apple is anticipating an iOS experience on the desktop for a long time coming.

Re: GitHub for Mac

#63
post #41
post #16

Earlier quoted context omitted.

I used Tower for a while, and I didn't have the chance to test Git for Mac yet (will do later today when I'll be using my Mac). One thing that Tower can do quite well is dealing with multiple remote repositories (e.g. github + heroku). If GitHub for Mac does that as well, I believe I'm going to switch to that.

it only works on github

Correction: It only works with a single 'origin' remote. It should work fine with any smart http git host. Someone in this thread mentioned it working just fine with Assembla.

Re: GitHub for Mac

#64

I wonder why they've released a client for OS X and not another OS―if anything, Windows is pretty lacking in git love. Whose is its target audience and the desired function? New users, to reel them in with a shiny UI? Or established users who don't use it much, to make the experience simpler? (And if it's established users who use it much―isn't the command-line faster for them?) If they want more users to use GitHub,…

Perhaps because it's easier to develop something like this for OS X?

Re: GitHub for Mac

#65

I wonder why they've released a client for OS X and not another OS―if anything, Windows is pretty lacking in git love. Whose is its target audience and the desired function? New users, to reel them in with a shiny UI? Or established users who don't use it much, to make the experience simpler? (And if it's established users who use it much―isn't the command-line faster for them?) If they want more users to use GitHub,…

Honestly I think it is the first platform because many of the github developers are Mac users.

Re: GitHub for Mac

#66

I wonder why they've released a client for OS X and not another OS―if anything, Windows is pretty lacking in git love. Whose is its target audience and the desired function? New users, to reel them in with a shiny UI? Or established users who don't use it much, to make the experience simpler? (And if it's established users who use it much―isn't the command-line faster for them?) If they want more users to use GitHub,…

Because we all use OS X. Build what you use first, expand from there.

Re: GitHub for Mac

#68
post #28

I hate all the visual clutter and unjustified complexity the new stylish iOS-like interfaces bring. Those interfaces are only good for Twitter and friends (and for screenshots). Some feedback: * Get rid of huge spacing everywhere (for example here: http://github-images.s3.amazonaws.com/blog/2011/mac-screensh... ) * Make animations go faster. * History should have preview pane with diffs (see Mail) instead of making m…

Have you tried GitX? What you described seems a bit more like GitX than what GitHub is trying to do here.

When I first fired this up, I made a tarball of one of the repos I'm currently working in (it has uncommitted changes) and started clicking around. I'd do something in the GitHub app, then go back to my bash prompt to see what happened. I was pretty confused when I switched branches and all my changes were gone. Then I went back and read the blog post. It auto-stashes when you switch branches. I also wondered what the heck the "Synchronize" button does, so once again, I referred to the blog post. It performs what they call a "smarter version of pull --rebase && push that reduces merge commits but doesn't rewrite your merges". Oh, really?

At that point I realized that GitHub has done the hard thing. They haven't re-created the git CLI tool in a GUI, they've created something different. They've created a tool that makes Git more accessible. Little things like auto-stashing when you switch branches will confuse git veterans, but it will make Git much easier to grok for newcomers because of the assumptions it makes about your git workflow.

I see great things in this app's future. It's probably not for everyone. If you're a proficient git cli user, and you like it that way, then you're probably best off sticking with what you've got. Maybe explore some of the more traditional Git GUI clients like GitK or GitX, but keep in mind, that's not what this is.

Re: GitHub for Mac

#69
I'm sorry, but in the world of awesomely-licensed Qt and other cross-platform toolkits, why would you go out of your way to build a native app on Mac libraries and only release it for a single platform?

I can understand that OS X probably has the biggest share of GitHub visitors, but git is fully open source, GitHub seem to very much like open source, and in the spirit of that I'd expect a native app that works on as many platforms as possible.

Re: GitHub for Mac

#70
post #17

Free, too. GitHub don't mess around. Any plans for putting it in the Mac App Store?

Yes. But the update experience for Mac App Store apps is so bad right now that it's a bit discouraging.

What about the update experience do you find so bad/discouraging?
Post reply on HN