Hacker News new | past | comments | ask | show | jobs | submit login

I more or less consider it a solved problem.

You're mostly going to hear from people here who are annoyed with Git or otherwise more interested in the topic of version control than the median developer. For me, I think it provides a quite robust and well thought-out set of primitives, and then composes them upwards in ways which are about as good as one can expect.

Some stuff obviously isn't well supported. Using the same Git repo to hold large binaries as well as source code is not well supported unless you reach for LFS - that's the biggest downside I see.

Fossil would be my next bet. I'm waiting for someone to make an archaeology.co to rival GitHub.com for it.




>I think it provides a quite robust and well thought-out set of primitives

The existence of the staging area is a poorly thought out part of the design. No other VCS uses it because it was a bad idea that makes the simple case of commuting changes more complicated.

>Fossil would be my next bet. I'm waiting for someone to make an archaeology.co to rival GitHub.com for it.

Which is exactly why fossil will not be the next big VCS. Ignoring all of the projects on Github add forcing people to move to a less featureful, less integrated, less familial forge just to use a new source control system is a hard sell. The approach of Sapling and Jujutsu where they support the git protocol so that they can be used Github will make them much easier to adopt since it can happen incremenetally and it fully replace git for people.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: