This is a talk on potential improvements to Git. Hipp is the author of SQLite and also Fossil, a distributed version control system. In the talk, he compares Git, Fossil and some other VCS and...
This is a talk on potential improvements to Git. Hipp is the author of SQLite and also Fossil, a distributed version control system. In the talk, he compares Git, Fossil and some other VCS and proposes tenand a bonus improvements to Git itself.
Title is kinda clickbaity, but I don't regret falling for it.
Interesting talk. A lot of points seem to be somewhat nitpicky or rather niche. Point #2 (a simpler mental model) definitely would be nice - the underlying data model for git isn't easy for new...
Interesting talk. A lot of points seem to be somewhat nitpicky or rather niche. Point #2 (a simpler mental model) definitely would be nice - the underlying data model for git isn't easy for new programmers to grasp, but its rather important to understand when using git outside of a very simply workflow. I don't know how you change that, since git isn't solving a simple problem. But I do see that being a key component of "the next big version control" - it'll be easier to use and won't require the user to understand the low level mechanics behind it.
Its been 4 years since that video. I'd be curious to know how many of these points have been added to git or are available as additions to git.
Off the top of my head, you can use git daemon to mimic some portion of a "git serve" command. See this blog post and this stackoverflow for some examples (both of which are from before the video was published on youtube). It doesn't do a nice graphical implementation of the data in the git repo - but I'd be surprised if no one has written a script to serve that data. But perhaps its rather complicated, which is why sites like github and gitlab and bitbucket make big bucks doing that for us.
This is a talk on potential improvements to Git. Hipp is the author of SQLite and also Fossil, a distributed version control system. In the talk, he compares Git, Fossil and some other VCS and proposes tenand a bonus improvements to Git itself.
Title is kinda clickbaity, but I don't regret falling for it.
Interesting talk. A lot of points seem to be somewhat nitpicky or rather niche. Point #2 (a simpler mental model) definitely would be nice - the underlying data model for git isn't easy for new programmers to grasp, but its rather important to understand when using git outside of a very simply workflow. I don't know how you change that, since git isn't solving a simple problem. But I do see that being a key component of "the next big version control" - it'll be easier to use and won't require the user to understand the low level mechanics behind it.
Its been 4 years since that video. I'd be curious to know how many of these points have been added to git or are available as additions to git.
Off the top of my head, you can use
git daemonto mimic some portion of a "git serve" command. See this blog post and this stackoverflow for some examples (both of which are from before the video was published on youtube). It doesn't do a nice graphical implementation of the data in the git repo - but I'd be surprised if no one has written a script to serve that data. But perhaps its rather complicated, which is why sites like github and gitlab and bitbucket make big bucks doing that for us.