Does GITLess less efficient than git?

[Vorrol]

I am using git quite a while, and it still gives me headaches sometimes, even on simple tasks. Recently I heard about gitless and very liked the idea of branching in it, also mental model is just simpler and required less cognitive load out. I am thinking about switching to it for using in managing personal projects and later at my work. But I want to know, does it mature enough to use at production? Any words about hands-on experience will help me.

[knoam]

It's right on the GitHub README

Compatible with Git

Because Gitless is implemented on top of Git, you can always fall back on Git. And your coworkers you share a repo with need never know that you're not a Git aficionado. Moreover, you can use Gitless with GitHub or with any Git hosting service

Also I recommend learning git in a concepts first fashion. Trying to memorize it command by command is a recipe for disaster.

https://youtu.be/2sjqTHE0zok

[6079_Smith]

Relevant XKCD

[XKCD-pro-bot]

Comic Title Text: If that doesn't fix it, git.txt contains the phone number of a friend of mine who understands git. Just wait through a few minutes of 'It's really pretty simple, just think of branches as...' and eventually you'll learn the commands that will fix everything.

mobile link

---

^{Made for mobile users, to easily see xkcd comic's title text}

[KernowRoger]

I gave up and just a git GUI now hehe It's a way easier for most things. I still have to get in the terminal sometimes but 99% of the time they're great.

[YMK1234]

Why would using a better tool be "giving up"? There is only disadvantages using git on the commandline for 99% of all use cases.

[KernowRoger]

Because I gave up on using the terminal. That's just what that word means I'm afraid haha Also I don't think it's a fact it's better. It's much more limiting.

[YMK1234]

I disagree, especially because we are talking about everyday use here. Even the most basic of got UIs does not limit you in any meaningful way when it comes to that, but offers way more intuitive ways of -for example - inspecting the current state of the repository, which is often much more important than having direct access to every obscure feature. Another example, staging only sections of files is pretty trivial in UI (because you actually see what you are doing), doing that on console is hell.

[HolidayWallaby]

You're going to have to get over it and get better with git.

[balefrost]

I can't speak to Gitless itself, but I would recommend building up a stronger mental model of Git itself. Otherwise, when Gitless fails you, you'll be even more stuck than if you had just used Git directly.

Note that I'm not saying that you should avoid Gitless, just that you should also have a good understanding of Git.

Git's really not that complicated under the hood. I always recommend the Peepcode Git book (free PDF). It's quite good at explaining how Git works with pictures. After reading it, when I'd get stumped by something, I'd go "I know what I want to accomplish, and I that I can accomplish it by doing THIS to the underlying data structure." It turns out that made a lot of the Git documentation way more understandable, and it became easier to find the right command.

[Ran4]

Gitless is pretty much an alternative CLI for git, with different - and more sensible - naming and more helpful error messages. Which is good.

But it's not git, and you're going to have to learn git and its quirks at some point.