161–170 of 214 posts
This looks awesome, but is it too soon for a feature request? I'd love a side-by-side diff view, FileMerge style.
while we're at the feature requests, multiple accounts? I've got a "business-y" type one and a personal one
Earlier quoted context omitted.
You're not describing a bubble, "making something I want" isn't some outlandish absurd thing for developers and designers do. Bubble is rapidly outpacing pivot for most misused word.
He meant bubble as in 'echo-chamber', and in that sense of the word it isn't overused. It's not outlandish or absurd to design something you might want, but it is a bit silly to ignore a larger market with the same underlying need.
> Beyond that, one-third of our traffic uses Macs. It's not a small market for us.
Will be interesting to see if they integrate issues and wiki into this. For a first release though, I'm impressed. Edit: Also would love to see this integrated with notifications so I can get Growl popups.
There are already plenty of okay Git GUI clients out there to manage your repository locally, but what I miss is the ability to edit (and preview!) the wiki locally. You can sync the contents via git, but then you are left with editing the raw source files directly.
That's cool and all, but a Windows client would make a lot more business sense. There are already a couple of nice git clients for Mac. There aren't for Windows. And I assume github is targeting SMB with its paid offerings. Unless you're a design shop or a hip startup, odds are you're not running OS X. Based on my unscientific data, most companies have the devs working on Windows (or occasionally Linux).
> Unless you're a design shop or a hip startup They are the latter. Welcome to the San Francisco bubble, where you think everyone uses iPhones and Macs, because in your world everyone does. It's the same reason Twitter has a Mac app but not a Windows app. They build these things for themselves (and arguably they should).
Earlier quoted context omitted.
We built the Mac app because 1) we wanted it 2) to learn how a desktop client should work prior to tackling other platforms. Beyond that, one-third of our traffic uses Macs. It's not a small market for us.
I can't argue with your reasoning But I just switched from self-hosted SVN to Github and it was painful for our Windows devs. Offer a stupidly easy upgrade path from TortoiseSVN to Github and I would have joined a long time ago. In fact I'd pay extra for that. I think I am not alone.
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…
I think overall this is a very nice product, even though some of the loading is a wee bit slow (even on an i7 iMac). It adds a very nicely done, easy to navigate interface for the times I want to visually manage stuff.
9/10 times I'll use the command line to do stuff, but this makes other aspects of code management go much quicker for me.
Solid 7/10 from me.
First time an application has been unsupported on my Core Duo (32bit) Macbook Pro. Is there a reason for it, does the application really require a 64bit OS, or did the GitHub guys just forget about us early Intel Mac owners?
That's cool and all, but a Windows client would make a lot more business sense. There are already a couple of nice git clients for Mac. There aren't for Windows. And I assume github is targeting SMB with its paid offerings. Unless you're a design shop or a hip startup, odds are you're not running OS X. Based on my unscientific data, most companies have the devs working on Windows (or occasionally Linux).
> Unless you're a design shop or a hip startup They are the latter. Welcome to the San Francisco bubble, where you think everyone uses iPhones and Macs, because in your world everyone does. It's the same reason Twitter has a Mac app but not a Windows app. They build these things for themselves (and arguably they should).
Earlier quoted context omitted.
Fair points, indeed! I can clarify: 1. Floating inspectors drive me bananas unless they can be pinned in the app "wrapper". 2. A new window for every document makes me crazy, because I like to use tools like Witch for doc-level tab switching. 3. The push away toward full screen apps and in-app file management is, IMO, a good thing.
1. Floating inspectors drive me bananas unless they can be pinned in the app "wrapper". I'm with you here, mostly. iCal's switch from sidebar in 10.4 to popups and floating inspectors in 10.5 is painful. On the other hand, Acorn's floating tools window is good. 2. A new window for every document makes me crazy, because I like to use tools like Witch for doc-level tab switching. I'm not so into tabs for documents, but…
1. Floating inspectors: Inspectors in general are getting better and I definitely prefer when it is well integrated into the view without interrupting my flow. They have a good start; further work is needed (not sure what though)
2. I think even tabs are a mistake now. We learned a lot from iOS about how to well integrate multiple views into a seamless interface. Tabs are kind of unnecessary imho now; we need something better.
3. Full screen isn't what I think the best aspect is - we do want to be able to view different apps at the same time. Case in point: - I have this chrome tab open on the right hand side of my iMac monitor - 3 terminal windows on the left hand side - My vc pitch in PPT on my second monitor's right hand - My PPC ad management software open on the second monitor's left side.
Restricting to one screen for an app isn't the right way I think, but an in-between method is. Funnily enough, I think Windows 8 almost nailed it.
As for in-app file management: YES. iCloud, Dropbox and a myriad of other systems all working together have such potential. I can't wait.
Earlier quoted context omitted.
We built the Mac app because 1) we wanted it 2) to learn how a desktop client should work prior to tackling other platforms. Beyond that, one-third of our traffic uses Macs. It's not a small market for us.
I can't argue with your reasoning But I just switched from self-hosted SVN to Github and it was painful for our Windows devs. Offer a stupidly easy upgrade path from TortoiseSVN to Github and I would have joined a long time ago. In fact I'd pay extra for that. I think I am not alone.