Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Designing GitHub for Mac

warpspire.com

Post reply on HN
Print view View original

41–50 of 80 posts

Re: Designing GitHub for Mac

#41

Post by lrz »

cdcarter wrote: post #17

He makes great points about MacRuby. I started tooling around with it for an app a few months ago, and though it was a great interface, it didn't make working in Cocoa any easier, and I still had to learn a lot of weird technology choices in Cocoa. Though, I think the difficulty of making a complex GUI in Cocoa shines in the OS X world. It's a lot harder to make a working UI, so you want to get the design right the f…

Well, MacRuby is a language on top of Objective-C. You can use Cocoa with it, but you should be able to use the Chameleon framework too, assuming it is GC-friendly (otherwise, adding GC support shouldn't be hard). His points don't make much sense to me.

Re: Designing GitHub for Mac

#42

Post by natesm »

On the images/code drawing points: are there any benchmarks for this? I've been writing meticulous CGGradient type stuff recently, should I just make a gradient in Photoshop and call it a day instead?

Re: Designing GitHub for Mac

#43

Post by kenneth_reitz »

mechanical_fish wrote: post #38
kisielk wrote: post #34

Earlier quoted context omitted.

Couldn't the app use your username / password to connect to github the first time and then generate an SSH key pair which it would use from that point forward? That seems like the best compromise of security and easy of use to me.

Then the client would only work easily with Github. That would be very sad for those of us who deploy Git repos on other servers than Github. As it is, I'm pretty sure this is using standard HTTPS auth with Git, which is not that hard to support.

The client works fine with other Git servers, and uses your standard SSH keys.

"Death to the SSH key" applies only to GitHub interactions — getting a list of your repos, for example.

Re: Designing GitHub for Mac

#46

Post by lukeschlather »

kneath wrote: post #37
gregschlom wrote: post #24

> Death of the SSH key. People should be able to connect to GitHub with their GitHub username and password. This sounds like a wrong design decision. I wish nobody could log into my github account using anything but my SSH keys. This is also true of my AWS account: my ec2 instances are protected by SSH keypairs, but if anyone gets my AWS password, he has full control over everything. I'm not a security expert, but SS…

Since GitHub launched, you've been able to access your repositories via username/password (and add/remove ssh keys via the web interface). But remember — we're talking about client security. If someone steals/owns your personal machine it's actually much easier to gain access to SSH Keys than find your username/password (since an alarming number of people use passwordless ssh keys). Aside from that though — SSH Keys…

>(since an alarming number of people use passwordless ssh keys).

Then I'll amend gregschlom's comment to further say I wish passwordless ssh keys did not exist.

Re: Designing GitHub for Mac

#47

Post by pornel »

mmphosis wrote: post #44

Auto Save and Versions http://www.apple.com/macosx/whats-new/auto-save.html

These APIs are not well-suited for git-like version control.

They're document-oriented, rather than project oriented (or if you present git repository as bundle, you lose nifty per-document presentation).

iCloud may force creation of versions (commits?)

There's no branching. There's lots of locking and exclusive access.

Post reply on HN