Hacker News Reader

Comment by 999900000999 | Hacker News Reader

I would love to see a better git compatible VCS. I'm not feeling good about self hosting my version control.

https://github.com/martinvonz/jj is a promising alternative which fixes many of the design mistakes of Git, but can still interact directly with Git repositories.

Funny that Google requires employees to say "THIS IS NOT A GOOGLE PROJECT, THIS IS MY 20% PROJECT", yet reserves the right to say "I can have this" at any point.

Well, Google literally paid the salary of the developer while he was developing it. This isn't even like it was something done on his personal time that Google can stake ownership in since he works there. It literally is a work product, which just happens to be not supported by Google.

The first one is a warranty issue. The second one is a work-for-hire-copyright-law issue.

Thanks this looks pretty cool.

Honestly all I want is a git command that runs

git commit . -m timestamp git push

I probably do something like that every 20 minutes or so.

This is the right approach.

Since everyone just stepped on to use git without thinking, "Because Linux uses it", we have to endure the pain of unfriendliness of git and it's already like S3 where if you want to start any competing project, it has to be git compatible to even get started.

I suppose there are SubGit, hg-git, bzr-git trying to keep their respective version control while facing git on the other end.

Somehow people miss these messages and projects like Bazaar got ran over by git for no good reason.

> We take great pride in making Bazaar easy to learn, easy to use and suitable for everyone, not just elite hackers.

> Ease of use is a core value for Bazaar and there are many places where our focus on usability shines though.

http://doc.bazaar.canonical.com/migration/en/why-switch-to-b...

I thought people were looking for tools with this philosophy.

I remember using git when everyone in my org was still on svn, using git-svn extension. I did not care who used it -- I just wanted lightweight branches with easy rebase/amend. Keeping all the extra checkouts, old copies and .diff files around was getting annoying.

Today, all the VCSs offer more-or-less the same set of features (Fossil being somewhat an exception in that regard). But in the past, there were quite a lot of differences. A lot of arguments for git were very technical.

Git compatibility pretty much rules out the radically different approaches that might actually be better enough to outcompete it. Like:

- Patch-based VCS (darcs, pijul)

- CRDT (live collaboration)

- Image-based systems (Smalltalk)

- Features that require the server to do stuff that Git protocol won’t do, like push notifications

In other words, I can’t imagine leaving Git unless it’s as big of an upgrade as Git was to SVN. And you can’t do that while being wire compatible.

This is the premise for got. https://gameoftrees.org/

Reply on news.ycombinator.com