Sourcegraph Blog

Hi there, Sourcegraph CTO here. Code search remains free for individual devs, and I hope you'll continue using us for your projects! https://about.sourcegraph.com/code-search/pricing

We have lots to reflect on given the feedback here on HN. We were honestly a bit blindsided by the number of people who appear to be using open source Sourcegraph, or who really wanted to use it but found the process too difficult. Part of this is because we had a zero telemetry policy for the open source distribution. Perhaps that was a mistake in hindsight, but introducing telemetry there would've been another can of worms!

Now that the usage is more visible, it's actually kicked off a lively internal discussion. We're going to take some time to gauge the size of the user community and figure how we can best support it. Aside from individual use being free (still the case) and making deployment more straightforward (through something like code search in App), are there other things we can do to make it easier to adopt? Sorry about the confusion here, we should have handled this better. But the silver lining is we realized there were a lot of users of Sourcegraph that we didn't know about and we're now discussing how best to engage and support you all. I do hope you'll take the chance to pop into our Discord and say hello and continue with feedback that can help us make the best decisions for our users.

Sourcegraph CEO here. Thanks for posting this!

The blog post has a GIF of code intelligence (hovers, go-to-definition, and find-references) in a diff. There's another nifty animated GIF on our homepage showing the code intelligence integration for GitHub: https://about.sourcegraph.com/. Our new tour at https://about.sourcegraph.com/docs/tour has some links to try it out on open-source code (although for the real experience, you can follow the steps on our homepage to run it inside your own organization to use it with your internal code). And check out the overview/FAQ at https://about.sourcegraph.com/docs/overview.

Finally, we have an awesome team based in SF and around the world (Arizona, South Africa) building Sourcegraph. We're growing quickly as more devs bring Sourcegraph into their companies and their companies adopt Sourcegraph (we can show you nice-looking charts :). If you want to learn more about joining the team, email me at sqs@sourcegraph.com with the thing you'd most like to improve about or add to Sourcegraph.

Others said this different ways, but I think the scenarios where you don't get an immediate segfault at the bad read/write are the trickiest ones--hard to debug, at least. One flavor is, say, writing past the end of a slice b/c you read the pointer from one slice and len/capacity from another. If it segfaults, it might be later when the clobbered object is next used.

A few years back someone at Dropbox mentioned tricky prod-only races were a real problem for them sometimes, for instance: https://about.sourcegraph.com/go/go-reliability-and-durability-at-dropbox-tammy-butow/#What-does-Dropbox-find-difficult-about-Go

That's where I start dreaming about best-effort detection of races in production binaries or even just reducing the chances of torn reads. Years back there might have been other options, like explicit private vs. shared heaps with more controls on the shared heap, but there seems to be a more restricted set of choices now.

Sourcegraph | REMOTE | Full-Time | Full-stack Engineer, Support Engineer, Enterprise Product Manager, Demand Generation Manager, Digital Growth Marketing Manager | https://sourcegraph.com

Sourcegraph is a code intelligence platform that makes it easy to read, write, and fix code–even in big, complex codebases.

We are building Cody, an AI coding assistant that uses code search and code intelligence to help devs quickly understand what's happening in code and generate new code that matches the best practices in your codebase. Cody supports AI-enabled autocompletion, fixing bugs, refactoring, test generation, code explanation, and answering high-level questions. You can read Steve Yegge's post on why Cody's code context engine differentiates it from the fast-moving field of AI dev tools: https://about.sourcegraph.com/blog/cheating-is-all-you-need.

Apply here: https://grnh.se/0572f98b4us

Sourcegraph (https://sourcegraph.com) | Software Engineer | San Francisco, CA or REMOTE

Sourcegraph is building tools that software developers love and use on a daily basis. Code search allows you to instantly search across all of your company's private code to find what you are looking for (definitions, examples, error messages, etc.). Code intelligence gives you hover tooltips, find references, and jump to definition while you are looking at code in your browser on Sourcegraph or on your code host.

We are a small team of mostly engineers who love to code, and we already have big/recognizable/global companies paying for our product. If you are passionate about making the world better through software, come join us!

Stack: Go, TypeScript, GraphQL, Docker + Kubernetes

Jobs page: https://about.sourcegraph.com/jobs

My big problem with Zig is that Andrew Kelley is promising a lot of features, but doesn't really deliver much. Zig still can't proper handle UTF-8 strings [1] in 2022, which is kind of unfortunate, because it's a `requirement`. In a `recent` interview[2], he claims that Zig is faster than C and Rust, but he refers to extremely short benchmarking that has almost no value in the real world.

At least Rust, as blamed and loved as it is, delivered a stable compiler and people started working on the ecosystem (in the first years, most packages were working only on nightly, but at least there were crates available). The ecosystem for zig is insignificant now and a stable release would help the language.

[1] https://github.com/ziglang/zig/issues/234
[2] https://about.sourcegraph.com/podcast/andrew-kelley/