hanwenn

7 ms·

31.
by hanwenn 3y ago
Not in use that I know
32.
by hanwenn 3y ago
At the time that I started Zoekt (2016), Google's internal codesearch used suffix arrays for the string matching, which the team wasn't happy with, presumably because of the algorithmic complexity and indexing slowness. The Codes
33.
by hanwenn 3y ago
Russ Cox' trigram approach uses document IDs for the posting list, which makes the index much smaller, but gives less precise (ie. slower) matching. This is mentioned in the design doc at https://github.com/sourcegraph&
34.
by hanwenn 3y ago
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, S
35.
by hanwenn 3y ago
One can write conditions using the search query language, see https://gerrit-review.googlesource.com/Documentation/config-...
36.
by hanwenn 3y ago
Submit blocking is not only a feature targeted at admins (they configure how submit criteria), but also for users: users have to know if their change is ready to be submitted. IIRC, The result of a failing Prolog rule was a single string, w
37.
by hanwenn 3y ago
Not sure what "push at Google" means. For full context: the idea to use Prolog came from the project founder. In retrospect, it was a terrible idea, because almost nobody knows or likes Prolog, and that includes the SWEs at Google
38.
by hanwenn 3y ago
SSH traffic is encrypted, so to an observer, the packages look like random data already.
39.
by hanwenn 3y ago
According to the Alzheimer society, "Current research provides no convincing evidence that exposure to trace elements of aluminum is connected to the development of dementia." [1] Because Aluminium is extremely common in the earth
40.
by hanwenn 4y ago
(I wrote most of Zoekt) The github code search looks like an impressive piece work (congrats!). That said, I'm curious about the nuances regarding corpus size. Their blog post claims they have 115 Tb of source code, but that a position
41.
by hanwenn 4y ago
I am the manager for the Gerrit team at Google. I can assure you that the 'reviewers-by-blame' plugin is not currently used on any Google Gerrit instance.
42.
by hanwenn 5y ago
This. In the early days of Google search, there were lots of other search engines (Hotbot and Altavista come to mind), and they were crap compared to Google.
43.
by hanwenn 5y ago
Most croissants are factory-made these days, frozen and then baked off on location, both for supermarkets and bakeries (also many French bakeries). Keuringsdienst van Waarde had a good episode on it, https://www.npo3.nl/keur
44.
by hanwenn 5y ago
Booking takes a 20% cut of the reservation, so I expect every hotel to gladly you offer a 10% off the booking.com price.
45.
by hanwenn 5y ago
Hi, Zoekt author here. There are a bunch of interesting replies, but they all miss the point. The reason you can't use bytes is a combination of two things: (1) code search supports case-insensitive matching. (2) the search algorithm u
46.
by hanwenn 7y ago
cs.opensource.google runs on Google's search infrastructure, so it's unlikely to be open sourced. https://github.com/google/zoekt is open source, but lacks cross-referencing, and has a more spartan UI.
47.
by hanwenn 7y ago
thanks! If you install sourcegraph, you get the same btw. Sourcegraph indexed search is powered by zoekt.
48.
by hanwenn 7y ago
It is the same tool.
49.
by hanwenn 7y ago
I supplied the 3,064 number. In Android, some of the changes get propagated to different branches by an automatic process. It's very much possible that the real number is lower by 10x or so (I didn't check)
50.
by hanwenn 7y ago
if climate change continues at today's pace, there won't be humans in 500 years from now.
51.
by hanwenn 7y ago
I was there when the name was selected. It turns out "blaze" suggests speed, which is why it was a popular name for other software, and some of it was registered as trademark.
52.
by hanwenn 7y ago
The money is not made on the lumber, but on agriculture. I recently read that, most of the deforested regions are used for low-density cattle (0.5 cow / hectare), which gets transformed into beef, mainly for export.
53.
by hanwenn 9y ago
For people interested in searching code using an open source solution, you might be interested in Zoekt too, github.com/google/zoekt. There is a demo site where you can search 30G of source code (including the Linux kernel, Androi
54.
by hanwenn 9y ago
If you want to have an open source index search, you can try out github.com/google/zoekt/ . See here for a demo site: https://cs.bazel.build/ For example: https://cs.bazel.build/search?q=r%3At
55.
by hanwenn 11y ago
most of the non-google code is stored in a special subdirectory, and AFAICT, it's less than 10% of the total.
56.
by hanwenn 11y ago
The reason Google developed Piper was basically that Perforce couldn't scale beyond a single machine, and our repo was getting too large to even be usable on the biggest, beefiest x86 server that money could buy (single machines with t
57.
by hanwenn 12y ago
I guess if you want to integrate Go tools with builds in other languages. If you are using pure Go for your entire ecosystem, there is not much point in using Bazel, as the "go" tool is very capable for that scenario.
58.
by hanwenn 12y ago
I'm not a Gradle expert, so take this with a grain of salt. Gradle a single-threaded execution in some parts (I believe it may be configuration?), because the build-rules are written in a full blown language with access to the filesyst
59.
by hanwenn 12y ago
http://bazel.io/docs/FAQ.html - "What about Windows? We have experimented with a Windows port using MinGW/MSYS, but have no plans to invest in this port right now. Due to its Unix heritage, porting Bazel is s
60.
by hanwenn 12y ago
Bazel uses checksums to determine if builds are up-to-date, but shortcuts the checksumming if metadata (timestamp, filesize) have not changed between builds.

More ›