Live data from Hacker News

GitKraken: git GUI Client for Windows Mac and Linux

gitkraken.com

161–170 of 180 posts

Re: GitKraken: git GUI Client for Windows Mac and Linux

#161
post #65

Earlier quoted context omitted.

To be honest, html-based scroll lists are usually much faster than native one. Reason: Very obsolete UI framework for Mac.

This is totally backwards. HTML has no good elements for long lists at all, leading to janky techniques like "infinite scroll." But NSTableView was designed from the start with very long lists in mind. Try opening a large repo and scrolling a list of commits in GitKraken. You'll see large blank areas that get filled in after a few seconds. Now try it in, say, GitUp, which uses NSTableView: it is perfectly smooth.

I don't see any complex NSTableView in GitUp, they definitely use something other. When i worked at Telegram, we worked hard to make default lists smooth and it is almost impossible. Eventually main client became Qt-based instead of native frameworks. All other Git tools also very slow on my MPB Retina. All of them are laggy in lists and only lists.

Having nothing good for long lists doesn't matter as rendering pipline on OSX didn't updated for a years. Almost everything in UI on OSX is still software rendered instead of GPU. And Chrome extensively use GPU for rendering and that outperforms everything.

Re: GitKraken: git GUI Client for Windows Mac and Linux

#162
post #42

The applicatino asks you to register with my email address for further "communications related to GitKraken or Axosoft". There is no way to skip this step, you have to provide an email address ––and pay attention to "OR"... No thanks, buddy. First thing I tried is dropping a git repo folder to the window, didn't work. When I click the open button I can see the Javascript animation glitching on my 'Early 2015 i5 2.7 G…

If you're on OS X I recommend gitup. Very fast and clean. Although if I remember correctly, it does ask for an email address.

Whoa thank you for this, I love it! I do wish there was a Windows version, but it will be a nice-to-have while working on OSX.

Re: GitKraken: git GUI Client for Windows Mac and Linux

#163

I personally never use GUI clients for git, the CLI does exactly what it's supposed to do, efficiently, quickly in a stable reproducible manner, most GUI clients are for people who just don't want to learn to use the CLI properly. But some tips for your project: 1-Lose the forced email registration 2-Easy on the Luxury, we're devs not divas 3-The beta agreement is just way too scary to take the product seriously, exa…

Whenever you make an action using a GUI, you can clearly see what options are available to you, even if you're not using them. It's unreasonable for every person to invest the time to fully internalize the capabilities of every tool they use. The more (good) GUIs available, the better.

Re: GitKraken: git GUI Client for Windows Mac and Linux

#164

Earlier quoted context omitted.

You can click on the files in the right-hand pane to get the diff. Right-click for more options. I've been using the beta(!) for a few weeks and I think it's a promising product. I also don't think software should be completely disqualified for not being open-source (, buddy).

Thanks for pointing this out, I also couldn't figure out how to see a diff. I am not a fan of this layout. It makes it a bit difficult to get a feel for what the changes were in a quick glance.

I had a similar sense with the app. Despite the very slick UI, it just felt awkward and inconvenient in all sorts of little ways. I couldn't quite get at the info I wanted -- or couldn't do so fluidly. I couldn't quite do what I needed -- or couldn't do so fluidly.

I gave up on it in under an hour, which is kinda record time for me. I gave SourceTree a couple days, GitX/GitY/etc each got multiple hours, etc.

Re: GitKraken: git GUI Client for Windows Mac and Linux

#165

Earlier quoted context omitted.

I hate to be that guy, but you're paying $70 for that? What does that offer over, say SourceTree, Atlassian's free offering. From a quick glance, they look pretty similar to me.

Am I the only one who remembers when $70 was cheap for anything development related? Either it's good enough to save you 5-10 minutes a day where it's obviously worth $70 or it's not, and isn't worth any price (well maybe a dollar or two if you are, say, a collector of git clients).

The problem isn't the cost in money, it's the cost in time and inconvenience. It sort of manifests in two ways. First, I build my professional workflow around a tool that can simply cease to exist in a few days/weeks/months/years...it puts me at the mercy of the maker of the tool, often needlessly. Second, software that costs money tends to be closed source, which is at odds with community efforts that can improve and shape the software over time, as well as maintain it should the original developer move on. So those issues are the problem, not the $70.

Re: GitKraken: git GUI Client for Windows Mac and Linux

#166

I personally never use GUI clients for git, the CLI does exactly what it's supposed to do, efficiently, quickly in a stable reproducible manner, most GUI clients are for people who just don't want to learn to use the CLI properly. But some tips for your project: 1-Lose the forced email registration 2-Easy on the Luxury, we're devs not divas 3-The beta agreement is just way too scary to take the product seriously, exa…

Last time I saw GitKraken mentioned, I must admit I chose not to try it due to the license (which reads more like a NDA).

Re: GitKraken: git GUI Client for Windows Mac and Linux

#167

Earlier quoted context omitted.

Am I the only one who remembers when $70 was cheap for anything development related? Either it's good enough to save you 5-10 minutes a day where it's obviously worth $70 or it's not, and isn't worth any price (well maybe a dollar or two if you are, say, a collector of git clients).

The problem isn't the cost in money, it's the cost in time and inconvenience. It sort of manifests in two ways. First, I build my professional workflow around a tool that can simply cease to exist in a few days/weeks/months/years...it puts me at the mercy of the maker of the tool, often needlessly. Second, software that costs money tends to be closed source, which is at odds with community efforts that can improve an…

I disagree as all of those problems exist with SourceTree as well, which is what the parent was comparing it to.

Re: GitKraken: git GUI Client for Windows Mac and Linux

#168
post #11
post #9

Earlier quoted context omitted.

We actually have programmers who don't want to get involved with git...

> We actually have programmers who don't want to get involved with git... What do they prefer? Zip files, or something with a slightly different interface but equivalent complexity (e.g. mercurial) ?

Believe it or not, these guys are still using Visual Source Safe. They find "git pull, git checkout -b, git commit -a, git pull, open merge request on gitlab" too cumbersome for their day-to-day activities.

Re: GitKraken: git GUI Client for Windows Mac and Linux

#169

Earlier quoted context omitted.

The problem isn't the cost in money, it's the cost in time and inconvenience. It sort of manifests in two ways. First, I build my professional workflow around a tool that can simply cease to exist in a few days/weeks/months/years...it puts me at the mercy of the maker of the tool, often needlessly. Second, software that costs money tends to be closed source, which is at odds with community efforts that can improve an…

I disagree as all of those problems exist with SourceTree as well, which is what the parent was comparing it to.

Agreed.

Re: GitKraken: git GUI Client for Windows Mac and Linux

#170

Earlier quoted context omitted.

Which is weird, seeing as the git license is GPL 2. I mean, I find it weird that one can build a product completely around a GPL project, and somehow not make it GPL. The whole point of the GPL is to restrict derivatives. Yet, somehow this has been mutated to become "links to a library," as if the technical fact that the product links to some code over an API boundary is different, legally speaking, than calling it w…

Legal derivative works under copyright law of a particular computer program are not the same thing as programs which functionally interact with them -- functional interaction doesn't make a work derivative.

But what if the entire core functionality of the program relies on an open source program? This is the case here, I would argue.

ps. I realize that in a technical sense my comment is "wrong", hence the downvotes, but what I'm getting at is, doesn't this horribly break the spirit of the GPL?

Post reply on HN