Sourcegraph Blog

100% agree, debuggers are often neglected. Chrome's debugger is one of the exceptions. Java has great debuggers too. Debuggers are about the dynamics of the program... I'm thinking more about the static structure of the codebase. Tools like sourcegraph [1] address some of that. The STEPS report [2] comes to mind for other cool ideas in this direction: it is easier to navigate the code if there's less of it! 1: https://about.sourcegraph.com/ 2: http://www.vpri.org/pdf/tr2012001_steps.pdf

Sourcegraph CTO here. This is great news and we're looking forward to incorporating this into Sourcegraph's existing Python support (https://about.sourcegraph.com/), so users get all the code intelligence improvements in their code reviews and code browsers. Thanks for open sourcing!

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 [email protected] with the thing you'd most like to improve about or add to Sourcegraph.

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

I'm sorry to hear that. We have made a lot of improvements to Cody recently. We had a big release on Oct 4 that significantly decreased latency while improving completion quality. You can read all about it here: https://about.sourcegraph.com/blog/feature-release-october-2023 We love feedback and ideas as well, and like I said are constantly iterating on the UI to improve it. I'm actually wrapping up a blog post on how to better leverage Cody w/ VS Studio, that'll be out either later today or sometime tomorrow. As far as feedback though: https://github.com/sourcegraph/cody/discussions/new?category=product-f… would be the place to share ideas :)

We (Sourcegraph) have other features to stay competitive. One thing we have been working on indexing other code hosts like Eclipse Foundation, Crates.io, etc. We put this together anticipating these questions: https://docs.sourcegraph.com/getting-started/github-vs-sourcegraph We also just launched Search Ranking and Relevance: https://about.sourcegraph.com/blog/new-search-ranking More to come! And BTW we are happy to have competition, GitHub is a great brand and it will only make code search better for all developers.

Extensions are being deprecated anyway https://about.sourcegraph.com/blog/release/4.0#:~:text=Your%20favorite…

There is also a company called SourceGraph which parses the AST of the various languages and lets you get CLion-like features with regex search. https://about.sourcegraph.com/

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/

Yeah, I'd bet on https://about.sourcegraph.com. Fully focused on code search and are still light years ahead.

Big fan of Caddy as well. I recently listened to the Sourcegraph Podcast episode with Matt Holt. Pretty great episode, would recommend! https://about.sourcegraph.com/podcast/matt-holt/

I looked at https://about.sourcegraph.com/ but it seems...difficult, or just doesn't work for what i want, or similar. What do i want? javascript code that searches a tree (Chrome bookmarks) and returns the Nth+ leaf node that is not a folder, not a javascript: or data: URL, and return that node/bookmark and its 'N' value. ...and searchcode.com reports "There was an error processing your search. Please try a new search term."

Glad to hear it :) If you have any feedback we'd love to hear it, as well. We went 100% all-remote at the start of the year, and historically over 50% of over our team has always been remote. This has been a really good boon for us as we started writing down and documenting even more of our processes, etc. in a handbook: https://about.sourcegraph.com/handbook

I've used sourcegraph quite a bit for my Haskell project. It absolutely changed the way I've browsed code on the web. Also love their organization around a Master Plan: https://about.sourcegraph.com/plan You can tell they've been influenced by a certain Mafia.. Power to the Sourcegraph team.

Something that is not by Google but which you would probably like - SourceGraph. Has commercial options but it is OSS. https://about.sourcegraph.com/

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

I believe Upsource ( https://www.jetbrains.com/upsource/ ) and Sourcegraph ( https://about.sourcegraph.com/ ) are both code-aware in that sense.

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.

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-drop… 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? https://about.sourcegraph.com/

Sourcegraph might be better: https://about.sourcegraph.com/

(2007) More recently, author promotes an AI dev tool (Cody) from Sourcegraph, where he is Head of Engineering: https://about.sourcegraph.com/blog/introducing-steve-yegge

Hey, Diego Comas here, Sourcegraph's Head of Security. The only email addresses that were exposed were those of users who have accounts on Sourcegraph.com, not those of the installers or users of Sourcegraph self-hosted or cloud instances. Note that sometimes users have accounts on both platforms, though (e.g. for license key management). And as you mention, while we do collect the email addresses of the initial installers of self-hosted instances only, for security, product, and marketing updates per our TOS and privacy policy(https://about.sourcegraph.com/terms/privacy), those email addresses were not exposed since they are not stored on Sourcegraph.com.

> There simply aren't any tools that can plug into a massive codebase with millions of lines. If Sourcegraph's offering (https://about.sourcegraph.com/cody) has limits I'm not aware of, this is just a matter of time. But in my experience, this is a "nice to have" rather than a "must have" when it comes to the benefits of GenAI as it applies to coding.

It does have your entire codebase context using the Claude 100k context model. You can have a look at this white paper for more info about how Cody uses the right context: https://about.sourcegraph.com/whitepaper/cody-context-architecture.pdf

My first impulse with this new wave of tooling is to poke at the privacy policy, especially given there's only the free trial version available... https://about.sourcegraph.com/terms/cody-notice seems generally reasonable though, so that's appreciated. Wouldn't mind a more transparency/confirmation on who the partner LLM entities are (Anthropic?), and some verbiage on the downstream impacts of their terms. Should be interesting to give it a test-run with some embedded projects.

still vocally is! https://about.sourcegraph.com/blog/all-you-need-is-cody

Based on your use of "campaign" (the older name for Batch Changes), it sounds like you were looking into Sourcegraph about 2.5 years ago or before that. Lots has changed since then. We recently released a new indexer scip-clang (https://about.sourcegraph.com/blog/announcing-scip-clang), which we've used to successfully index large codebases like Chromium. The indexer relies on a JSON compilation database (same as our older indexer lsif-clang) which is easy to produce from CMake, Bazel, Meson, Make etc. We've also added support for cross-repo code navigation for C++ recently. (https://about.sourcegraph.com/blog/c-cpp-cross-repo)