18 ms·
A Git story: Not so fun this time
- hoistbypetard 2y agoThanks for sharing a fun read. Bitkeeper was neat, and my overall take on it mirrors Larry McVoy's: I wish he had open sourced it, made his nut running something just like github but for Bitkeeper, and that it had survived. I only had one interaction with him. In the early '00s, I had contributed a minor amount of code to TortoiseCVS. (Stuff like improving the installer and adding a way to call a tool that could provide a reasonable display for diffs of `.doc` and `.rtf` files.) I had a new, very niche, piece of hardware that I was excited about and wanted to add support for in the Linux kernel. Having read the terms of his license agreement for Bitkeeper, and intending to maintain my patches for TortoiseCVS, I sent him an email asking if it was OK for me to use Bitkeeper anyway. He told me that it did not look like I was in the business of version control software (I wasn't!) and said to go ahead, but let him know if that changed. I use git all the time now, because thankfully, it's good enough that I shouldn't spend any of my "innovation tokens" in this domain. But I'd still rather have bitkeeper or mercurial or fossil. I just can't justify the hit that being different would impose on collaboration.
- nmz 2y agoI wouldn't put fossil in that list of collaboration, since its not really a collaborative tool, or more like, there are barriers to that collaboration, like creating a username for each fossil repository. That's a huge barrier in my view. It would be nice if there was something like a general auth identity that can be used everywhere but that's still not implemented. FWIW, mercurial seems to have an advantage over git, and that support for BIG repositories which seems to be provided by facebook of all people, so until facebook moves to git, mercurial lives on.
- thunderbong 2y agoYou can have one repository and link all the others to it via "Login Groups" https://www.fossil-scm.org/home/doc/trunk/www/caps/login-groups.md https://www.fossil-scm.org/home/doc/trunk/www/caps/login-gro...
- phyrex 2y agoFacebook doesn’t really use vanilla mercurial but its own scale-oriented rust fork. It’s open sourced as “sapling”
- sunshowers 2y agoLike I tell lots of people, check out Jujutsu. It's a very Mercurial-inspired-but-better-than-it UI (the lead dev and I worked on Mercurial together for many years) with Git as one of the main supported backends. I've been using it full time for almost a year now.
- JoshTriplett 2y agoI would love to use jujutsu, and it seems like a great model. I think it'd be a bad outcome if the world starts building top a piece of software with a single company owner and a CLA, though. I hope that the CLA goes away one day.
- sunshowers 2y agoNote that the CLA does not transfer copyright, so "single company owner" is not accurate from a copyright perspective.
- JoshTriplett 2y agoIt's accurate from the perspective of "there's a single company with the right to change the licensing arbitrarily".
- ilyagr 2y agoNo, it is not accurate. That is not what Google's CLA says. (Though there are other CLAs out there that are closer to what you describe) (*Update:* Though IANAL, you should read the child comment and the CLA itself and make up your own mind. https://cla.developers.google.com/about/google-individual https://cla.developers.google.com/about/google-individual. The rest of my comment is mostly independent of the previous paragraph). OTOH, IANAL, but AFAIK anyone can fork `jj` and sell a proprietary product based on jj (and distribute it under pretty much whatever license they like, with very few restrictions) because it is currently Apache licensed, but that is unrelated to the Google CLA. Let me conjecture even more wildly about things I don't know. The following is a guess on my part. One way to interpret this is that Google tends to publish their projects under Apache, and there is no need to demand that people transfer copyright to Google. By releasing your work under Apache, you are already giving Google (or anyone else) all the rights it needs. AFAIK, the main purpose of the Google Individual CLA is to have you sign a statement claiming that you own the rights to your own work and didn't give up those rights to your employer.
- yencabulator 2y agoI was a heavy user of BitKeeper. To me, Git is almost exactly like a ground-up cleaner rewrite of BitKeeper. Gitk and git-gui are essentially clones of the BitKeeper GUI. I don't understand why you'd want to keep using BitKeeper.
- hoistbypetard 2y agoI think my memory is probably colored by BitKeeper being my first DVCS. I was never a heavy user of it. I was exposed to BitKeeper when I was managing my team's CVS server. On my next team, we moved to svn, which always felt like cvs with better porcelain from a developer perspective, but when administering that server fell onto my plate, I liked it a lot better than CVS. And I thought BitKeeper would be nicer from a developer perspective. Then on my next team, we used mercurial. I really, really, really liked mercurial, both as a developer and as a dev infrastructure administrator. It also sucked a lot less on Windows than git or BitKeeper. The last time I had to decide for a new team, mercurial and git were the obvious options. I went with git because that was clearly what the world liked best, and because bringing new team members up to speed would require less from me that way. All that goes to say... my direct comparison of git and bitkeeper came from when bitkeeper was mature and git decidedly was not. Then I lumped it in with mercurial (which I really would still prefer, right now) and fossil (ditto). You're probably exactly right about BK.
- cmrdporcupine 2y agoConceptually git is more powerful. But I recall the bitkeeper CLI being far more sensible in its interface.
- yencabulator 2y agoIt had its own weird quirks, and sometimes revealed that it was a front for a single file with a lot of funnily-formatted lines. We're just separated from it in time, and you can only truly hate what is familiar.
- deleted 2y ago[deleted]
- jdougan 2y agoIt is open source, Apache license 2. Check at https://www.bitkeeper.org/ https://www.bitkeeper.org/
- yjftsjthsd-h 2y agoAnd in light of the history, https://github.com/bitkeeper-scm/bitkeeper https://github.com/bitkeeper-scm/bitkeeper is funny on several levels.
- pests 2y agoHe is quoted at the end of the article saying that was what they should have done, and they did have a public offering, but hindsight and yadda yadda.
- superfish 2y agoGreat read! I’m sure I’m not the first to point out that Junio (the appointed git “shepherd”) works at Google where mercurial is the “recommend local vcs” internally instead of git.
- ilyagr 2y agoLarge parts of Google rely on Git, most notably Chrome and Android. Also, it is a good thing if Junio can do his job independently of Google's immediate needs.
- mulmboy 2y ago> Additionally, Petr set up the first project homepage for Git, git.or.cz, and a code hosting service, repo.or.cz. These websites were the “official” Git sites until GitHub took over. Is this true? I thought GitHub had no official affiliation with the git project
- jimbobthrowawy 2y agoI think some github employees have written code that went into git, but it's not an official affiliation. The quotes on "official" imply non-official to me. i.e. official seeming to people who don't know any better.
- arp242 2y agoThat's why "official" in in quotes. As in: "de-facto standard".
- cxr 2y agoNot really. git-scm.org is the de facto "official" site for the Git project in about the same way that French is the de facto "official" language of France. They meant exactly what they wrote: GitHub took over hosting duties for the official Git site (because they did).
- roywashere 2y agoThe git repo is on kernel.org nowadays with mirrors on repo.or.cz and GitHub. But I think they mean here what the official git project ‘site’ is with docs and so on. And that is now https://git-scm.com/ https://git-scm.com/ and indeed as the article describes that was initially set up by GitHub people, to promote git
- xiwenc 2y agoIt’s been awhile since i actually finished reading an article this long. Very well written! I tried to find out who the author is or how come he/she knows so much. No luck. Anyone else knows or OP care to chip in?
- hackan 2y agoHere: https://news.ycombinator.com/item?id=40849363#40854063 https://news.ycombinator.com/item?id=40849363#40854063
- cryptonector 2y ago> In a 2022 survey by Stack Overflow, Git had a market share of 94%, ... > Never in history has a version control system dominated the market like Git. What will be the next to replace Git? Many say it might be related to AI, but no one can say for sure. I doubt it's getting replaced. It's not just that it's got so much of the market, but also that the market is so much larger than back in the days of CVS. It's hard to imagine everyone switching from Git. Switching from GitHub, feasible. From Git? That's much harder.
- jbaber 2y agoIt does feel like asking "What will replace ASCII?" Extensions, sure, but 0x41 is going to mean 'A' in 5050 AD.
- eliangcs 2y agoAuthor here. I don’t think ASCII is the right comparison. True, it would be really hard for anything to compete with Git because a lot of infrastructures we have are already deeply integrated with Git. But think about x86 vs. ARM and how AI might change our ways of producing code.
- mmphosis 2y agoUTF-8
- account42 2y agoThat validates gp's point though: UTF-8 doesn't replace ASCII, it extends it. All valid ASCII text remains valid UTF-8 while retaining the same meaning. With the momentum behind git it will be hard for something incompatible replace it, but an extended git could catch on.
- fragmede 2y agoGit shortcomings are well known by this point, so "all" a successor project has to do is solve those problems. Git scales to Linux kernel sized projects, but it turns out there are bigger, even more complex projects out there, so it doesn't scale to Google-sized organizations. You would want to support centralized and decentralized operation, but be aware of both, so it would support multiple remotes, while making it easier to keep them straight. Is the copy on Github up to date with gitlab, the CI system, and my laptop and my desktop? It would have to handle binaries well, and natively, so I can check-in my 100 MiB jpeg and not stuff things up. You'd want to use it both as a monorepo and as multirepos, by allowing you to checkout just a subtree of the monorepo. Locally, the workflow would need to both support git's complexity, while also being easier to use than git. Anyway, those are the four things you'd have to hit in order to replace git, as I see them. If you had such a system, getting people off git wouldn't be the issue - offer git compatibility and if they don't want to use the advanced features, they can just keep using their existing workflow with git. The problem with that though, is that then why use your new system. Which gets to the point of, how do you make this exist as a global worldwide product? FAANG-sized companies have their own internal tools team to manage source code. Anywhere smaller doesn't have the budget to create such a thing from scratch but You can't go off and make this product and then sell it to someone because how many companies are gonna go with an unproven new workflow tool that their engineers want? What's the TAM of companies for whom "git's not good enough", and have large enough pocketbooks?
- cxr 2y agoThere's a screenshot purporting to be of GitHub from May 2008. There are tell-tale signs, though, that some or all of the CSS has failed to load, and that that's not really what the site would have looked like if you visited it at the time. Indeed, if you check github.com in the Wayback Machine, you can see that its earliest crawl was May 2008, and it failed to capture the external style sheet, which results in a 404 when you try to load that copy today. Probably best to just not include a screenshot when that happens. (Although it's especially silly in this case, since accessing that copy[1] in the Wayback Machine reveals that the GitHub website included screenshots of itself that look nothing like the screenshot in this article.) 1. <https://web.archive.org/web/20080514210148/http://github.com/ https://web.archive.org/web/20080514210148/http://github.com...>
- philipwhiuk 2y agoThanks - I was struggling to believe GitHub would have launched with something as bad looking - 2008 was not CERN era looking webpages!
- eliangcs 2y agoAuthor here. That's a good catch, thanks! I've replaced it with a newer screenshot from August 2008.
- cxr 2y agoLarry wants to call you and discuss two corrections to this piece ("one minor, one major"). I've already passed on your email address for good measure, but you should reach out to him.
- deleted 2y ago[deleted]
- dudus 2y agoI never heard the term porcelain before, but I liked this tidbit. "In software development terminology, comparing low-level infrastructure to plumbing is hard to trace, but the use of “porcelain” to describe high-level packaging originated in the Git mailing list. To this day, Git uses the terms “plumbing” and “porcelain” to refer to low-level and high-level commands, respectively. " Also, unrelated, the "Ruby people, strange people" video gave me a good chuckle. https://www.youtube.com/watch?v=0m4hlWx7oRk&t=1080s https://www.youtube.com/watch?v=0m4hlWx7oRk&t=1080s
- nyanpasu64 2y agoFYI Mercurial's developer is now known as Olivia Mackall; sadly the Google infobox has failed to pick up the updated information.
- eliangcs 2y agoUpdated, thanks.
- globular-toast 2y agoI've heard the story before but this was still fun to read. I didn't realise quite how rudimentary the first versions of git were. It really makes you wonder: was git the last opportunity to establish a ubiquitous version control system? Will there ever be another opportunity? Regardless of git's technical merits, one thing I'm extremely happy about is that it's free software. It seemed to come just before an avalanche of free software and really changed the way things are done (hopefully for good).
- ozim 2y agoIt created the avalanche. I don’t think scale of free software we have now would be possible without git and GitHub.
- shagie 2y agoTwo of the key features that were part of of early git that show much git was about support Linux kernel development: https://git-scm.com/docs/git-am https://git-scm.com/docs/git-am https://git-scm.com/docs/git-send-email https://git-scm.com/docs/git-send-email Git was built around supporting the linux kernel email lists. And while there are a number of other options out there that sprang up around the same time, many of them didn't fill the core need for git at that time - to reduce the stress / workload on Linus.
- sergius 2y agoThis story is missing the impact that Tom Lord's TLA had on the git design.
- cxr 2y agoPreviously: <https://news.ycombinator.com/item?id=32155067#32157109 https://news.ycombinator.com/item?id=32155067#32157109>
- JoshTriplett 2y ago> Tridge did the following. > “Here’s a BitKeeper address, bk://thunk.org:5000. Let’s try connecting with telnet.” Famously, Tridge gave a talk about this, and got the audience of the talk to recreate the "reverse engineering". See https://lwn.net/Articles/133016/ https://lwn.net/Articles/133016/ for a source. > I attended Tridge's talk today. The best part of the demonstration was that he asked the audience for each command he should type in. And the audience instantly called out each command in unison, ("telnet", "help", "echo clone | nc").
- luckydude 2y agoThis is completely untrue. There is no way that you could make a BK clone by telneting to a BK and running commands. Those commands don't tell you the network protocol, they show you the results of that protocol but show zero insight into the protocol. Tridge neglected to tell people that he was snooping the network while Linus was running BK commands when Linus was visiting in his house. THAT is how he did the clone. The fact that you all believe Tridge is disappointing, you should be better than that. The fact that Tridge lied is disappointing but I've learned that open source people are willing to ignore morals if it gets them what they want. I love open source, don't love the ethics. It's not just Tridge.
- JoshTriplett 2y ago> There is no way that you could make a BK clone by telneting to a BK and running commands. Those commands don't tell you the network protocol The network protocol, according to multiple sources and the presented talk at LCA, was "send text to the port that's visible in the URL, get text back". The data received was SCCS, which was an understood format with existing tools. And the tool Tridge wrote, sourcepuller, didn't clone all of BitKeeper, it cloned enough to fetch sources, which meant "connect, send command, get back SCCS". Anything more than that is hearsay that's entirely inconsistent with the demonstrated evidence. Do you have any references supporting either that the protocol was more complicated than he demonstrated on stage at LCA, or that Tridge committed the network surveillance you're claiming? And to be clear, beyond that, there's absolutely nothing immoral with more extensively reverse-engineering a proprietary tool to write a compatible Open Source equivalent. (If, as you claim, he also logged a friend's network traffic without their express knowledge and consent, that is problematic, but again, the necessity of doing that seems completely inconsistent with the evidence from many sources. If that did happen, I would be mildly disappointed in that alone, but would still appreciate the net resulting contribution to the world.) I appreciate that you were incensed by Tridge's work at the time, and may well still be now, but that doesn't make it wrong. Those of us who don't use proprietary software appreciate the net increase in available capabilities, just like we appreciate the ability to interoperate with SMB using Samba no matter how inconvenient that was for Microsoft.
- JoshTriplett 2y ago> In January 2006, the X Window team switched from CVS to Git, which wowed Junio. He didn’t expect such a big project like X Window to go through the trouble of changing version control systems. It's the "X Window System" or just "X".
- deleted 2y ago[deleted]
- blacklion 2y agoInteresting, this story quote (without attribution!) this comment by Larry McVoy himself on HN https://news.ycombinator.com/item?id=11671777 https://news.ycombinator.com/item?id=11671777
- zerocrates 2y agoThat part really should just be a straight quotation; the very light rewording of the original post feels in poor form.
- aidenn0 2y agoThe entire comment section on that post is a goldmine, thanks!
- kreetx 2y agoHe is now here as well :), though rather annoyed I would say. I guess business success doesn't bring happiness. Edit: There was another thread from him linked as well https://news.ycombinator.com/item?id=26205688 https://news.ycombinator.com/item?id=26205688
- janvdberg 2y agoExceptional read! I love it. It's the most complete history of git that I know now. Exceptional! I'd love to read more historical articles like this one, of pieces of software that have helped shape our world.
- noufalibrahim 2y ago+! to that. Great read. The field is young and accelerating. History is quite compressed. It's valuable to have articles like this.
- eliasson 2y agoDitto. This was a really nice read!
- deskr 2y ago> It's the most complete history of git that I know now. I wasn't going to read the story until I read your comment. I knew the summary of BitKeeper and the fallout, but wow this was so detailed. Thanks!
- fragmede 2y agothe dream machine was a good one, though a bit more historical. http://folklore.org http://folklore.org has a bunch of good Apple stories.
- OrangeMusic 2y agoIf you like computer/software history, I recommend the Abort Retry Fail[1] mailing list. [1] https://www.abortretry.fail/ https://www.abortretry.fail/
- OrangeMusic 2y ago(I meant 'newsletter' , not 'mailing list')
- ajkjk 2y agoDang this is such a good read.
- deleted 2y ago[deleted]
- metadat 2y ago> My biggest regret is not money, it is that Git is such an awful excuse for an SCM. It drives me nuts that the model is a tarball server. Even Linus has admitted to me that it’s a crappy design. It does what he wants, but what he wants is not what the world should want. Why is this crappy? What would be better? Edit: @luckydude Thank you for generously responding to the nudge, especially nearly instantly, wow :)
- luckydude 2y agoMy issues with Git - No rename support, it guesses - no weave. Without going into a lot of detail, suppose someone adds N bytes on a branch and then that branch is merged. The N bytes are copied into the merge node (yeah, I know, git looks for that and dedups it but that is a slow bandaid on the problem). - annotations are wrong, if I added the N bytes on the branch and you merged it, it will (unless this is somehow fixed now) show you as the author of the N bytes in the merge node. - only one graph for the whole repository. This causes multiple problems: A) the GCA is the repository GCA, it can be miles away from the file GCA if there was a graph per file like BitKeeper has. B) Debugging is upside down, you start at the changeset and drill down. In BitKeeper, because there is a graph per file, let's say I had an assert() pop. You run bk revtool on that file, find the assert and look around to see what has changed before that assert. Hover over a line, it will show you the commit comments to the file and then the changeset. You find the likely line, double click on it, now you are looking at the changeset. We were a tiny company, we never hit the claimed 25 people, and we supported tons of users. This form of debugging was a huge, HUGE, part of why we could support so many people. C) commit comments are per changeset, not per file. We had a graphic check in tool that walked you through the list of files, showed you the diffs for that file and asked you to comment. When you got the the ChangeSet file, now it is asking you for what Git asks for comments but the diffs are all the file names followed by what you just wrote. It made people sort of uplevel their commit comments. We had big customers that insisted the engineers use that tool rather a command line that checked in everything with the same comment. - submodules turned Git into CVS. Maybe that's been redone but the last time I looked at it, you couldn't do sideways pulls if you had submodules. BK got this MUCH closer to correct, the repository produced identical results to a mono repository if all the modules were present (and identical less whatever isn't populated in the sparse case). All with exactly the same semantics, same functionality mono or many repos. - Performance. Git gets really slow in large repositories, we put a ton of work into that in BitKeeper and we were orders of magnitude faster for things like annotate. In summary, Git isn't really a version control system and Linus has admitted it to me years ago. A version control system needs to faithfully record everything that happened, no more or less. Git doesn't record renames, it passes content across branches by value, not by reference. To me, it feels like a giant step backwards. Here's another thing. We made a bk fast-export and a bk fast-import that are compatible with Git. You can have a tree in BK, have it updated constantly, and no matter where in the history you run bk fast-export, you will get the same repository. Our fast-export is idempotent. Git can't do that, it doesn't send the rename info because it doesn't record that. That means we have to make it up when doing a bk fast-import which means Git -> BK is not idempotent. I don't expect to convince anyone of anything at this point, someone nudged, I tried. I don't read hackernews any more so don't expect me to defend what I said, I really don't care at this point. I'm happier away from tech, I just go fish on the ocean and don't think about this stuff.
- throw7 2y agoFun read. The licensing of bitkeeper was a real thing. Although I don't follow the kernel mailing list at all nowadays, I remember Alan Cox calling it out as buttkeeper. Good Times.
- deleted 2y ago[deleted]
- lawgimenez 2y ago> A heavily sedated sloth with no legs is probably faster I'm going to borrow this phrase from now on to everything slow.
- tretiy3 2y agoI have no experience with c and i wonder: why Linus decided that implementing merging should go with scripting language and not in c?
- hgo 2y agoThis is why I come to HN. Thank you to the author.
- mindjiver 2y agoThis really took me back. Back then before Git was a big thing (2010/2011-ish) I had the misfortune to work at a very large user of IBM Rational ClearCase and it was so awful. However it was so bad and so expensive that I managed to get tasked to "fix it". As part as figuring out how to do this I travelled to GitTogether 2011 from Sweden. Lots of Git folks from those days where there, at least I remember Junio, Peff and Shawn Pearce being there. I was so energised from it all I went back and formed a small team that migrated a colossal code base (oh the horror stories I have) over to Git over the next 2 years. The most rewarding thing I did early in my career. So thank to all of you that made this possible by creating Git, Gerrit and all the life saving tools this industry was missing! The passing of Shawn Pearce was really sad, but he won't be forgotten!
- rob74 2y ago> The bk clone/pull/push commands functioned similarly to git clone/pull/push. That sounds a bit backwards: actually Git works similar to BitKeeper (can't say to what extent, as I'm not familiar with bk), not the other way around.
- account42 2y agoThanks Andrew Tridgell for not letting the kernel get stuck with a proprietary source control. An example how sticking to your principles can make the world better in the long run even if it annoys people at first.
- samus 2y agoThe Kernel was not "stuck"; Linus is ultimately a practical man and was fine using it for integration work. The question whether or not switching to an Open Source solution would have eventually been raised again, but at the time it did what it was supposed to do.
- michaelcampbell 2y agore: licensing > You couldn’t use BitKeeper for version control if you were working on version control software. > You had to get BitMover’s permission if you wanted to run BitKeeper alongside other similar software. That just strains credulity.
- rasz 2y agoThis actually sounds like KryoFlux (floppy imaging hardware/software) EULA https://www.reddit.com/r/vintagecomputing/comments/buyj9f/til_that_computer_archivists_image_the_magnetic/epjwsut/ https://www.reddit.com/r/vintagecomputing/comments/buyj9f/ti... Even outcome was the same :) flurry of more reasonable competitors with fully open source GreaseWeazle offering the whole nine yards.
- devdao 2y agoRequesting permission from your source control tool vendor to be able to continue your work is nonsense. It's alive today! Sr.ht has categories of work you can't host too. Still marinating.
- dgfitz 2y agoSo we’re stuck with git because of rails, how amazingly poetic.
- daitangio 2y agoVery well written & nice article. I already knows a bit of the story. Just a plus: even Windows source code is on git! Which is pretty cool if you think about it. Open source wins
- jakubnarebski 2y agoRegarding *Codeville* version control system: if I remember it correctly, it used novel merge algorithm, which was often better than the diff3 merge algorithm that RCS, CVS, Subversion, Git and other version control systems use. However, if there was a problem with merge (a conflict), it was, from what I heard, much harder to resolve - because the algorithm was more complex. And with the introduction of the recursive merge the diff3 algorithm was deemed good enough in practice, easy to understand, and lacking sharp corner cases.