Live data from Hacker News

Gitless: a version control system

gitless.com

1–10 of 390 posts

Re: Gitless: a version control system

#4
> 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.

Re: Gitless: a version control system

#5
The approach of this experiment is interesting. But, as an experienced git user, I think it does not include easy access to very powerful and easy-to-learn features of git like "git * -p" which bring some interactivity in git commands.

Re: Gitless: a version control system

#7
To me the really bad thing about git is its command-line interface.

It has extremely verbose messages (writes out a lot of stuff that you don't need to know) and common use cases often requires multiple steps (ie. add, commit, push if you just want to send a change from your work machine a github repository).

Compare this to subversion which is much less verbose, and in general just have one operation pr. use case.

Re: Gitless: a version control system

#10

The approach of this experiment is interesting. But, as an experienced git user, I think it does not include easy access to very powerful and easy-to-learn features of git like "git * -p" which bring some interactivity in git commands.

I assumed all `git` commands would still be available even if one might prefer `gl` for some tasks, am I missing something?
Post reply on HN