News for hackers. Stuff that matters.
Re:Code Search at Google: The Story of Han-Wen and Zoekt by JohnMakin on Tuesday November 21, 2023 @01:52PM (#38368241)
I didn't start my tech journey til late 00's, so it's constantly surprising to me that something as ubiquitous as git only came out in 2005.

Is it possible at all this story helped spur the widespread adoption of git (the early implementation of this tool)?

Re:Code Search at Google: The Story of Han-Wen and Zoekt by dekhn on Tuesday November 21, 2023 @02:57PM (#38369187)
Before git, most people in my larger circle used RCS, a UNIX version control system from the early 80's. It was very limited (basically each file had its own side-file that contained revision data, and there was no project-wide file) but did its job. Many people moved over to VCS, which used RCS files but added project-wide files so you could manage a dir tree.

After that, I think many people moved to subversion, which had a lot more functionality for distributed VC, for exmaple there was a server. svn was popular for a while but building it was painful (due to berkeley db) and it sort of never grew. I invested a lot of time in (specifically apache with mod_dav and mod_dav_svn) but lost interest in VC after fighting with subversion.

git came along and from what i can tell it mainly had "it's by linus, and the kernel uses it" and "it's fast" and "something about reflogs". I use git day-to-day but I still; can't explain how git became so ubiquitous; I find using it outright painful.

Re:Code Search at Google: The Story of Han-Wen and Zoekt by dws on Tuesday November 21, 2023 @03:47PM (#38369852)
Lightweight branches was a huge selling point. If you didn't do them often enough that they were rote, branches in RCS/CVS/SVN required ritual sacrifice.
Re:Code Search at Google: The Story of Han-Wen and Zoekt by reportingsjr on Tuesday November 21, 2023 @03:50PM (#38369905)
Mercurial (aka hg) was also gaining popularity at the same time as git. The interface was a lot nicer and more sane than git, but it had some serious performance limitations that hampered it.

Both were definitely way better than SVN/CVS/etc.

Re:Code Search at Google: The Story of Han-Wen and Zoekt by dekhn on Tuesday November 21, 2023 @04:03PM (#38370093)
Yes, after using git for a few years I was introduced to Mercurial and it was like a breath of fresh air, although I'm also told hg added a number of things that made it much more usable, "right before I started using it".

Since I have limited brain capacity I focus my efforts on being able to use git, not hg, merely because it has so much marketshare.

Re:Code Search at Google: The Story of Han-Wen and Zoekt by cpach on Tuesday November 21, 2023 @04:39PM (#38370634)
Nit-pick: Did you mean CVS?
Re:Code Search at Google: The Story of Han-Wen and Zoekt by dekhn on Tuesday November 21, 2023 @04:43PM (#38370690)
Yes, CVS.
Re:Code Search at Google: The Story of Han-Wen and Zoekt by timr on Tuesday November 21, 2023 @06:10PM (#38371894)
You have a weird/selective perspective.

As someone who has used all of them in different companies since the 90s: RCS was ancient, even in the early 90s. Most widely found in things like UNIX source trees.

CVS came along later (mid/late 90s), and was much more widely used.

SVN came on the scene around the late 90s -- it was a massive improvement on CVS, and spread across open source and most professional shops like wildfire. Major sites like sourceforge were built on SVN, but also supported CVS.

Git only became prevalent starting around 2006-2008, and adoption was actually really slow because of its inherent complexity. When Github appeared, that was really when the shift started in earnest.

There were others along the way: MS SourceSafe, a moment when everyone was toying with Bitkeeper, etc., but these were as marginal as RCS.

Re:Code Search at Google: The Story of Han-Wen and Zoekt by paulryanrogers on Tuesday November 21, 2023 @09:00PM (#38373662)
Bazar was my first DVCS, used after SVN, and it became clear very quickly why Git used SHA revision IDs.
Re:Code Search at Google: The Story of Han-Wen and Zoekt by timr on Wednesday November 22, 2023 @01:48AM (#38375683)
Forgot about Bazar!
Re:Code Search at Google: The Story of Han-Wen and Zoekt by jonstewart on Tuesday November 21, 2023 @10:44PM (#38374512)
Subversion -was- a massive improvement over CVS but the effort to create it only started in 2000 and it was early 2004 when it went 1.0. I think it was at the 2003 OSCON when Fitz et al introduced it? Everyone in the audience was stoked, but it only had a few good years before git eclipsed it.
Re:Code Search at Google: The Story of Han-Wen and Zoekt by timr on Friday November 24, 2023 @11:30AM (#38405597)
Sounds right. I didn't look up the exact dates. Tons of folks were using it before 1.0, though.
Re:Code Search at Google: The Story of Han-Wen and Zoekt by zem on Wednesday November 22, 2023 @05:42AM (#38377507)
don't forget arch (aka "tla" for "tom lord's arch")! I played with it briefly back in the day but for some reason did not stick with it

https://en.m.wikipedia.org/wiki/GNU_arch

Re:Code Search at Google: The Story of Han-Wen and Zoekt by xarope on Wednesday November 22, 2023 @01:06AM (#38375270)
ah yes, I still remember the rcs ci / co workflow
Re:Code Search at Google: The Story of Han-Wen and Zoekt by dekhn on Wednesday November 22, 2023 @01:31PM (#38383112)
I mean I learned a lot back in the rcs days- I worked on a small team with a few million lines of code under RCS in a shared FS. The devs taught me about social locking protocol- basically, talking with your coworkers about what parts of code not to work on, because you'd have your hands down in the guts.

One of my first real accomplishments was migrating that codebase from RCS to CVS- which was relatively easy as CVS used RCS under the hood.

Re:Code Search at Google: The Story of Han-Wen and Zoekt by ajross on Tuesday November 21, 2023 @02:35PM (#38368809)
Git stepped into a source control ecosystem that was well-served (albeit contentious). People knew (or at least thought they knew) what they wanted from bk/svn/CVS/p4/rcs/sccs.

So git essentially was the "final form" that integrated all the various workflows and topped it off with a maximally-scaled use case (linux) that proved out the tool, drove innovation in integration/scripting/gadgetry, and provided a clear beacon for everyone else to adopt it. So it won.

But in 2004, if you asked around, everyone would have told you that a tool like this was coming at some point (even if they probably wouldn't have described it as very git-like!).

Re:Code Search at Google: The Story of Han-Wen and Zoekt by pgeorgi on Tuesday November 21, 2023 @04:03PM (#38370095)
If you squint a little, https://web.archive.org/web/20030629114010/http://www.venge.... is a fair approximation of some of the core ideas behind git (and Linus played with it and wrote a critique of its short-comings before starting git)
Re:Code Search at Google: The Story of Han-Wen and Zoekt by mettamage on Tuesday November 21, 2023 @05:41PM (#38371509)
That is so cool to see where Linus got some of his inspiration from. It made a few things more clear to me as to why git uses certain things.
Re:Code Search at Google: The Story of Han-Wen and Zoekt by jeffbee on Tuesday November 21, 2023 @02:26PM (#38368670)
I think it is odd that the story mentions git at all. Git5, the mentioned wrapper around piper, has only a niche audience when I last used it 5 years ago, and it was a demonstrated fact that the users of it were less productive than perforce users. Whether that was causal or not was unknown.
Re:Code Search at Google: The Story of Han-Wen and Zoekt by billllll on Tuesday November 21, 2023 @04:34PM (#38370553)
I agree there doesn't seem to be a good connection between work on version control and work on code search.

However, I don't think it makes sense to downplay git5. Anecdotally, basically everybody knew about it, and I'd constantly run into people using it (which is by itself noteworthy since nobody was exactly talking about version control all the time).

Git5 was at the time the most robust solution to chain commits, which was tedious bordering on impossible without some tool. Without definitive data, I wouldn't say users were less productive with git5: it definitely was a useful tool that people at least recommended for chain commits. I was definitely more productive with it.

There were a lot of footguns though, and I do think the hg wrapper that superseded it was way better.

Re:Code Search at Google: The Story of Han-Wen and Zoekt by hanwenn on Tuesday November 21, 2023 @04:27PM (#38370445)
Hi, I'm the Han-Wen from the title.

The story mentions git because git5 got me into developer tooling. More in particular, it put me in touch with Shawn Pearce who ran the Git/Gerrit team at Google. When I went to work for him, Shawn wanted to have codesearch support in Gerrit, and Zoekt was ultimately the outcome of my explorations in this space.

IIRC, Git5 was deleted approximately 5 years ago because Fig (the Hg based replacement) had taken over all the use cases

Re:Code Search at Google: The Story of Han-Wen and Zoekt by dag11 on Wednesday November 22, 2023 @03:10AM (#38376394)
Is Fig still kicking? I worked on it a bit as an intern back in 2014, but Mercurial has also been on its way out of mainstream support over the last few years. It was a really neat project!
Re:Code Search at Google: The Story of Han-Wen and Zoekt by hanwenn on Wednesday November 22, 2023 @03:58AM (#38376788)
See https://www.youtube.com/watch?v=bx_LGilOuE4. I think the plan is to replace to it with something based off JJ.
Re:Code Search at Google: The Story of Han-Wen and Zoekt by justrealist on Tuesday November 21, 2023 @02:57PM (#38369183)
Oh yeah. I remember merging SVN branches into production in 2010 or so.

It was a... special time. Let's not reminisce.