Hacker News Reader

> Gitless is an experiment to see what happens if you put a simple veneer on an app that changes the underlying concepts.

... changes them how exactly? A big part of what I like about Git is that its underlying concepts are simple and clear and feel like the right building blocks for version control. So I'm curious to know how they believe they can improve on that.

View on HN

It's not a quick answer but they cover this in the Gitless vs. Git section.[0] One main difference seems to be with branching "The main thing to understand is that in Gitless a branch is a completely independent line of development."

[0] http://gitless.com/#vs

By that, AFAICT they mean "a branch, in addition to being a commit pointer, contains all the files in the working directory".

And also the current merge state (though I'm not sure why I'd ever want to context switch away from a merge conflict resolution).

Reply on news.ycombinator.com