9 ms·
> But after closely studying Git I'm a little bit awestruck; Torvalds is a frickin' genius, a true visionary, and somehow managed to just "get it" and instantly
by kbenson 10y ago
> But after closely studying Git I'm a little bit awestruck; Torvalds is a frickin' genius, a true visionary, and somehow managed to just "get it" and instantly, in a flash of insight, come up with "the solution" for version control.
Wait, what? Git was the response from Torvalds to BitKeeper being proprietary and the author being upset with some kernel developers. It's basically taking what was then state of the art for DCVS and reimplementing it, not coming up with some new paradigm. It's a good program, and to my knowledge it was engineered well, but let's not rewrite history so Torvalds is the father of DVCS.
- rincebrain 10y agoSort of - DVCS did not have nearly as much general uptake before Git and Mercurial caught public attention, and none of the options available met Torvalds' featureset requirements. BitKeeper existed, a few projects used darcs, GNU arch and monotone existed but I don't think I ever encountered a project using either (the Canonical arch fork aside), and that's mostly a wrap for free or Free options. He may not be the father of a novel concept which he could write a paper about, but Git and Mercurial existing certainly coincided with the enormous uptick in DVCS usage and visibility. I suppose the difference in opinion about the term "father" just comes down to being about the theory behind the problem space or wildly successful implementation, and IMO "taking known solutions and putting them together in a more successful way" is novel enough to claim credit.
- _pmf_ 10y agoBitKeeper could have become GitHub + git in one entity if they made the client and hosting for FOSS free and charged for on-premises servers or private repos.
- Swizec 10y agoBut they didn't.
- jacobush 10y agoThey were stuck in a local optimum.
- gcp 10y agoDue to the ubiquity of git (and github) we (the users) are in the same case today.
- pjmlp 10y agoSadly with a much worse UX, as usual.
- rincebrain 10y agoA number of people have written nicer UXes for git, both CLI and GUI, but none of them have achieved critical mass that I've seen so far.
- pjmlp 10y agoThe critical mass only happened, because it is written by Linus and a must have for anyone working with the Linux source code. I very much doubt it would have succeed if it wasn't for those two factors. As such I would put it on the same basket as C, PHP and JavaScript, regarding adoption vs quality. As for Github, it is just the new Sourceforge, helped by the way they mismanaged it.
- _pmf_ 10y ago> As for Github, it is just the new Sourceforge, helped by the way they mismanaged it. Agreed; when GitHub is bought by the wrong company (when; not if), we'll be in a world of shit.
- gcp 10y agoIt's again due to the ubiquity. Even if I get stuck in a git UX hellhole, I can do a google search and be 99% sure the top result is a StackOverflow post explaining the steps needed to recover.
- peterwwillis 10y agoThe author doesn't know anything about VCS. And Bram is almost right in this case, Linus wrote Git in 10 days. The thing is, Git is pretty much the most horribly over complicated user tool in history. Learning how to use Git properly is more complicated than learning how to use Unix. Several times more complicated. I honestly would be more comfortable giving a modern team who had never seen a VCS before just plain old CVS, because even if it's horrible, at least it's simple and you can just work around the stupidity. Git will leave you trapped in a hellscape of reading manuals and howtos and bloating personal repositories, and not really do anything particularly great except feature branches. DVCS is great when you need it, but when you don't need it, it's annoying as hell.
- randomsearch 10y agoAre you criticising just git or DVCS? If the latter, try Mercurial if you haven't already used it.
- RJIb8RBYxzAMX9u 10y agoI wouldn't, and I'd tried using Mercurial for my personal random projects for a while. I gave up not because hg is inferior, but because when python, the language hg's written in, chose to migrate from hg to git, the war was truly over and lost. At the end of the day, a VCS is just a tool, one of many that I need to learn and use to do my job, and it's not worth the effort to learn both git and hg. Somewhat related anecdote: years ago I decided to learn Dvorak, but eventually switched back, because by the time I'd become proficient, my ability to type in QWERTY's completely gone. From what I'd read online at the time this was unusual: most people who learned Dvorak could switch back (& forth) within a few seconds to a few minutes. It took me probably a week or two to be able to touch type in QWERTY again, and maybe a month to get back to my original speed. And by then it was as if I'd never learned Dvorak at all. Anyway, the point of the story is: maybe I just have shit memory :-)
- peterwwillis 10y agoI used Mercurial very briefly just to evaluate it; it's fine. I'm criticizing git. And i'm also saying DVCS in general is more complicated than the most typical use case of VCS. Using Git for everything is like riding a bicycle with four derailleurs to pick up milk from the corner store. Granted, this is what I do right now; just because some technology is complicated or annoying doesn't mean I don't use it. But I wouldn't recommend it to others.
- deleted 10y ago[deleted]
- swang 10y agoi don't think he called torvalds the father of dvcs, merely he was the one who came up with the simplest and correct solution to handling merges (which is to let the user resolve most of the complex ones) and what about this line on the wikipedia page? > This [community] version of BitKeeper also required that certain meta-information about changes be stored on computer servers operated by BitMover, an addition that made it impossible for community version users to run projects of which BitMover was unaware. so not storing some changes locally, and being unable to access it if you don't have a paying version of the client seems to be really archaic compared to the simplicity of git. i could be misinterpreting what they mean by meta-information though.
- beagle3 10y agoLinus was moving off of BitKeeper, which obviously was some of the inspiration for git - but the underlying model is nothing alike. Git's data model is much simpler than CVS, RCS, Subversion, BitKeeper and basically anything else that existed at the time, and it was also much faster. The command line interface doesn't reflect this properly, but it's the underlying model that counts. Git is nothing like a reimplementation of BitKeeper - the closest inspiration and model is actaually Monotone, which had the same basic concepts but was slow and clunky. IIRC, Torvalds credited monotone/Hoare for using merkle trees (and other things)
- tomjakubowski 10y ago> The command line interface doesn't reflect this properly, but it's the underlying model that counts. Could you explain why, for a tool meant to be used by humans, the underlying model (which I agree is very elegant) counts more than the user interface?
- gcp 10y agothe underlying model (which I agree is very elegant) counts more than the user interface? It does not. But git exposes this all the time, so committed git users feel that's a good thing, because understanding it makes helps them to make sense of some of the worst parts of the UX.
- FatalBaboon 10y agoGit is the reference implementation of a protocol, and much like HTTP, you must learn it the hard way if you intend to be a professional in the domain. The mistake is to believe there is a U<I|X> in the first place. It does not, however, stop you from using one of the many graphical tools, that are fine for simple usage and will all eventually fall short. You could use a GUI to make complex HTTP routes, through proxies and DNS records via drag&drop, and then one day you'll have some weird DNSSEC error that the maintainer does not care about, and you will have to explain that to whoever is losing money. Acknowledging a problem is not as trivial as it was first thought is critical in our line of work in my opinion.
- cpks 10y agogit and mercurial are a million times more clever than a state-of-the-art DCVS like bitkeeper. It's a new data structure. It's a brilliant data structure. It's robust in ways even distributed databases aren't. It's fast. It's simple. It's clean. It's elegant. git made several additional breakthroughs in terms of working in terms of snapshots instead of diffsets, keeping much less data, and performing many computations late rather than early. In essence, these result in a system infinitely more flexible and expandable than prior version control systems. Adding new ways to change the source code in CVS required a whole new data format (SVN). In git, that's a minor change. The full power of git hasn't been anywhere close to exploited yet. The data model is very general-purpose, fast, and robust. It can do much more than just source control.