![]() It’s truly a game changer.īesides that, virtually every git command is simply easier to do in GitKraken. Click on a file, and you’re instantly looking at the diff of before and after. Click on a commit and see the details of what files were changed. Every branch, every merge, every commit is beautifully laid out. This is something people never see on the command line. ![]() Shojaee: When you first open GitKraken and point it to your repo, the thing that everyone notices instantly is the beautiful commit graph. InfoQ: What are some of the key pain points with Git that you feel GitKraken simplifies? It’s been on a steady and somewhat exponential growth curve, which has been great to see.īy the way, we already passed 1.4 Million users! Then their teammates get a sense that they are missing out, and it spreads. As GitKraken keeps getting better with every release (and on average, we have one or more releases every month!) more and more people are blown away by it. Shojaee: I don’t think there has been a single event or trigger that helped open the floodgates. What were some of the key tipping points in gaining traction for GitKraken? InfoQ: GitKraken now has over 1 million users which is quite an accomplishment in a very fragmented developer community. Their view is “show me a tool that makes me more productive, and I’m all over it.” We get 100% of those developers! Of course, the majority of developers are pragmatic. If a developer is very comfortable in the CLI, they are far more likely to dismiss any tool as something “real developers” don’t need, sight unseen. Some developers have a strong resistance to change. Shojaee: The biggest surprise shouldn’t have been a surprise at all. InfoQ: What are some of the biggest surprises you've learned along the way in building GitKraken? These are serious problems that we wanted to solve. We realized using the git CLI, it takes longer to bring new developers up to speed it’s far more likely that someone makes a catastrophic mistake and developers are more likely to avoid looking at a repo’s history to see what’s happening in their projects. Not all developers love the command line, and even if they do, ultimately they prefer to be more productive whenever they can. ![]() Hamid Shojaee: That’s precisely it! Git has traditionally been a tool used on the command line because nobody had spent the time creating a great graphical client for git. What led you and your team to originally create GitKraken? InfoQ: Git is historically a tool limited to those with a strong love of the command-line. InfoQ recently had the opportunity to interview GitKraken founder Hamid Shojaee to learn more about the development of their GUI for working with Git.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |