4 ms·
I don't understand all the criticism here. Personally, I don't like and barely ever use the index, I think that git is completely inconsistent with itself, and
by StavrosK 12y ago
I don't understand all the criticism here. Personally, I don't like and barely ever use the index, I think that git is completely inconsistent with itself, and find the design of gitless very consistent and easy to use.
I saw it the other day and learned to use it with only a page's worth of reading. Why are so many people confused?
- scrollaway 12y ago> I don't understand all the criticism here. Okay. > Personally, I don't like and barely ever use the index And there's why. A lot of us actually like and use the index a lot. It's incredibly powerful; one of git's most powerful features in fact.
- StavrosK 12y agoYou took one of my points and used it to dismiss my entire post. How does my not liking the index nullify the fact that git is entirely inconsistent?
- scrollaway 12y agoSorry, I did not mean to dismiss your entire post. Your wording suggests that you don't understand the criticism and confusion, but 90% of it in here (at the time of this writing) is due to the index being removed which is just: "wtf?". I agree that git is insanely inconsistent. I could talk about this for hours. I'd love a better porcelain. But gitless is removing some pretty critical stuff here. On the positive side, I really like the rest of their UI. I especially like the usage of "track" and "untrack" as core words.
- StavrosK 12y agoSome of the criticism is about the index, but most of the rest seems to be "why gitless?" and "how do I use it?", which are pretty well covered in the docs, I think. I agree with you that the removal of the index was a bit orthogonal to the end goal of making gitless more consistent. I do agree with their decision (because I don't find the index that useful), but you're right in that they dumped the baby out with the bathwater by going with simplicity rather than just consistency.
- chousuke 12y agoI read the page, but it's just a short introduction to some of the commands in gitless; and they're not at all different from git in concept either, except for the hiding of the index. It does nothing to answer "why" gitless exists, and why its creators think it's better than git. I identified several points where gitless' UI is in fact worse than git and as such am not likely to switch, but I am still interested in the rationale behind gitless' UI decisions. I often see people disparaging git's UI, but honestly, I can't see the problem anymore. Certainly there are weird bits (eg. git diff --cached) in the UI that I've learned by heart now, but I've also learned git's internals -- which doesn't require much investment at all since git is extremely simple -- and in light of that knowledge, git's behaviour is consistent and easily predictable.
- StavrosK 12y ago> Certainly there are weird bits (eg. git diff --cached) in the UI that I've learned by heart now That's the thing, if you've learnt them, gitless is useless to you. I'm not interested in learning whether a branch is deleted with -d or -D or git rm branch or whichever one they used for that specific command, so gitless making them all consistent is definitely an improvement.
- chousuke 12y agoI don't think you're seeing my point. The documentation doesn't do anything to convince the reader that gitless' UI is more consistent than git's. Let's pretend I'm a newbie. All I see in the documentation are a list of commands that have pretty much 1:1 mappings in git. How is it better?
- StavrosK 12y agoThey aren't, though. Have you seen how removals for anything use the same option, or there's no push or pull, or remotes are much more sane, or creating repos is the same regardless of whether you're cloning or initting? It's much more geared towards actions rather than commands.