[_pxkn]

Seems like this is based on Google's own internal code search tooling, something most engineers at Google rely on for every day code-level work. I personally can't even begin to imagine how I'd navigate the gigantic codebase without it.

(I work at Google)

[wrsh07]

I had this same fear as I left Google, but it turns out that a great ide (eg anything by jetbrains) can take you quite far.

It's a different work flow, but you simply don't need cs/ when your code base is orders of magnitude smaller

[arunaugustine]

Would you know if the Google cloud product for hosting git projects [1] uses the same underlying code search as the internal tool?

[1] https://cloud.google.com/source-repositories

[hanwenn]

It is the same tool.

[snazz]

It’s also used for https://source.chromium.org. I now host my monorepo on Cloud Source Repositories because it has a super nice integration with the rest of their products.

[joatmon-snoo]

If you crack open developer tools and watch the API requests go by, you'll be able to confirm that it's the same thing :)

[cromwellian]

Not really, this is a pale shadow of what the real CodeSearch inside Google does. I really wish the external ones had even 1/10th the functionality.

[coderdd]

Help https://github.com/TreeTide/underhood reach feature parity ;)

[zxienin]

what's 9/10th that internal one has?

[microdrum]

You'd use Sourcegraph, probably.

[mistrial9]

what is the constant phone-home activity on that opaque container they send as SourceGraph.. It is occassionally the case that devs have too-fast machines, so their code isn't seen on ordinary equipment. With SourceGraph and other inner-network-devs tools, the amount of chatty traffic and build dependancies seems seriously off-putting, trending to useless with ordinary network.

[voz_]

This seems like a bad attitude. Perhaps you could constructively ask for a sourcegraph-lite that does less, in return for less deps / networking complexity?

[slimsag]

I am a dev at Sourcegraph, I'd be very open to any feedback.

You can firewall off Sourcegraph 100% for complete confidence, and aside from the first admin's email address (so we can notify them of any security updates) we only send back aggregated anonymous usage statistics which we are extremely transparent about: https://docs.sourcegraph.com/admin/pings

We sell developer tools, not user data.

[jsjddbbwj]

Maybe the problem is that to disable telemetry you have to contact support and pray they like you, instead of giving a configuration option.

[slimsag]

Ah, yeah, that's fair. I'll forward this feedback onto the team.

The option is documented in our config docs, though, and also appears in the config editor's autocomplete in the app if you type `telemetry`, though, so it's not really a secret https://docs.sourcegraph.com/admin/config/site_config#disabl...

[enriquto]

How long do you estimate we will be able to use this before google inevitably kills the project?