LWN: Comments on "Searching code with Sourcegraph"

Searching code with Sourcegraph

hazmat — Sun, 23 Aug 2020 11:40:07 +0000

This type of "open source" is a imo disturbingly common trend, elastic, timescaledb, etc. As an oss contributor it effectively taints contributors by even doing something as simple as looking at the log or a diff in a repo as commits are often co-mingled, it represents fairly community hostile behavior imo. Elastic for example has gotten in the habit of suing other developers building on the oss (search guard).

Searching code with Sourcegraph

jezuch — Sat, 22 Aug 2020 13:42:46 +0000

Not sure if it qualifies as "relatively recent", but the earliest tool for structural search (and refactoring) I'm aware of is James Gosling's Jackpot circa 2000 (it now lives on as part of NetBeans IDE). Linux developers should also be familiar with Coccinelle, so-called "semantic search" tool used to find and fix bugs automatically, and also for widespread refactorings. There's also my favourite feature of Intellij IDEA :) I'm kind of a connoisseur of static analysis and structural search/replace tools so it's good to see another one out there!

Zoekt & trigram background

hanwen — Wed, 19 Aug 2020 09:12:13 +0000

For those interested in trigram search, I did a talk on Zoekt that folks might find interesting. See here: https://www.youtube.com/watch?v=_-KTAvgJYdI

Searching code with Sourcegraph

jkingweb — Wed, 19 Aug 2020 01:02:18 +0000

Having the proprietary bits be visible is a nice feature. I suppose you could build your own and have some assurance that there's no code you're not aware of lurking in there?

Searching code with Sourcegraph

riking — Tue, 18 Aug 2020 23:31:38 +0000

https://github.com/sourcegraph/sourcegraph/pull/11575 was inspired by this, by the way. Looks like it's still in progress.

Searching code with Sourcegraph

riking — Tue, 18 Aug 2020 23:29:10 +0000

We're running a SourceGraph instance for our (public, open source) monorepo at https://cs.tvl.fyi and it works pretty well!
I've noticed that not having LSIF does hurt reference lookup for extremely common phrases and variable names. This is obviously a solvable problem, we just haven't gotten it set up yet.

We use a nginx hack to have everyone be logged in as "Anonymous" (https://cs.tvl.fyi/depot/-/blob/ops/nixos/www/cs.tvl.fyi....).