3 ms·

Sourcegraph raises $125M at $2.6B valuation for universal code search

25 points by welder 5y ago

sqs 5y ago
Sourcegraph CEO here. Here's what we're doing with the money to make code search better and better in the future: https://about.sourcegraph.com/blog/the-future-of-code-search/ https://about.sourcegraph.com/blog/the-future-of-code-search... Happy to answer any questions. If you've used Sourcegraph, please share what you liked and what needs to be better!
- SahAssar 5y ago
  How does sourcegraph consider related fields like copilot or sentry (I consider it related since the mapping is a search of a codebase based on a stacktrace with metadata)? Are those fields that you are considering or are you focused on search?
  - sqs 5y ago
    We're focused on search. Devs spend most of their time reading and understanding code, not writing code (Copilot) or following stack traces (Sentry). Things like Copilot and Sentry are super interesting, but our role is helping devs read and understand code better. We have a lot more work to do there. Sourcegraph does show Sentry info overlaid on code (https://sourcegraph.com/extensions/sourcegraph/sentry https://sourcegraph.com/extensions/sourcegraph/sentry), and we will probably experiment with more "AI-for-reading/understanding/maintaining code" stuff in the future.
- jasonmar 5y ago
  Does Sourcegraph support Scala, COBOL, RPG, PL/1? Beyond the languages in the docs, how much work is required to use any of these languages? https://microsoft.github.io/language-server-protocol/implementors/servers/ https://microsoft.github.io/language-server-protocol/impleme...
  - mariacraig 5y ago
    Sourcegraph PM here. Both Scala and Cobol are supported out of the box through search-based code intelligence (https://srcgr.ph/3xDPYcs https://srcgr.ph/3xDPYcs). We don't currently support RPG and PL/1. We also offer precise code intelligence (https://srcgr.ph/3hBPnlT https://srcgr.ph/3hBPnlT) that's powered by the LSIF protocol, this requires some setup and is currently available for Go(https://srcgr.ph/2U847Ac https://srcgr.ph/2U847Ac), Java(https://srcgr.ph/3r7quBT https://srcgr.ph/3r7quBT), TS/JS(https://srcgr.ph/3B57DMy https://srcgr.ph/3B57DMy) and C++). We have an easier path to supporting Scala in the future due to our Java indexing work, at the moment we don't have a concrete timeline for it.
caithrin 5y ago
Congratulations, clearly a massive achievement. Reading your post this jumped out at me: “ Cross-language compiler-accurate code navigation” The word navigation does a lot of work. Could you say more?
- olafurpg 5y ago
  I'm an engineer on the code intel team at Sourcegraph. You can try out compiler-accurate code navigation here https://sourcegraph.com/github.com/sourcegraph/sourcegraph@24798dbdf7a36b63475571e291831ef8b507fd1c/-/blob/lib/codeintel/lsif/conversion/errors.go?L15:35#tab=references https://sourcegraph.com/github.com/sourcegraph/sourcegraph@2... See "Go to definition" and "Find references". The general idea is that you should be able to navigate your codebase online with Sourcegraph similar to how you would navigate the code with a local IDE (IntelliJ, VS Code). The benefits of Sourcegraph become more pronounced once the size of the codebase grows, especially across multiple repositories, and you're working with a large team of developers.
deleted 5y ago
[deleted]
mrkramer 5y ago
I wouldn't be surprised if Google acquires this at this point.
- sqs 5y ago
  We're going to remain an independent company, not be acquired. We've got a strong underlying business and tons of future growth (code search has very low penetration today, and we're working hard to change that). If Google acquired us, would you be more or less likely to use Sourcegraph? If Google had a competing product, would you trust it more or less than our product (assuming all else is equal)? I believe the answers to both questions point to Sourcegraph being most valuable as an independent company. :)

25 points by welder 5y ago

sqs 5y ago

Sourcegraph CEO here. Here's what we're doing with the money to make code search better and better in the future: https://about.sourcegraph.com/blog/the-future-of-code-search/ https://about.sourcegraph.com/blog/the-future-of-code-search... Happy to answer any questions. If you've used Sourcegraph, please share what you liked and what needs to be better!

SahAssar 5y ago
How does sourcegraph consider related fields like copilot or sentry (I consider it related since the mapping is a search of a codebase based on a stacktrace with metadata)? Are those fields that you are considering or are you focused on search?
- sqs 5y ago
  We're focused on search. Devs spend most of their time reading and understanding code, not writing code (Copilot) or following stack traces (Sentry). Things like Copilot and Sentry are super interesting, but our role is helping devs read and understand code better. We have a lot more work to do there. Sourcegraph does show Sentry info overlaid on code (https://sourcegraph.com/extensions/sourcegraph/sentry https://sourcegraph.com/extensions/sourcegraph/sentry), and we will probably experiment with more "AI-for-reading/understanding/maintaining code" stuff in the future.
jasonmar 5y ago
Does Sourcegraph support Scala, COBOL, RPG, PL/1? Beyond the languages in the docs, how much work is required to use any of these languages? https://microsoft.github.io/language-server-protocol/implementors/servers/ https://microsoft.github.io/language-server-protocol/impleme...
- mariacraig 5y ago
  Sourcegraph PM here. Both Scala and Cobol are supported out of the box through search-based code intelligence (https://srcgr.ph/3xDPYcs https://srcgr.ph/3xDPYcs). We don't currently support RPG and PL/1. We also offer precise code intelligence (https://srcgr.ph/3hBPnlT https://srcgr.ph/3hBPnlT) that's powered by the LSIF protocol, this requires some setup and is currently available for Go(https://srcgr.ph/2U847Ac https://srcgr.ph/2U847Ac), Java(https://srcgr.ph/3r7quBT https://srcgr.ph/3r7quBT), TS/JS(https://srcgr.ph/3B57DMy https://srcgr.ph/3B57DMy) and C++). We have an easier path to supporting Scala in the future due to our Java indexing work, at the moment we don't have a concrete timeline for it.

caithrin 5y ago

Congratulations, clearly a massive achievement. Reading your post this jumped out at me: “ Cross-language compiler-accurate code navigation” The word navigation does a lot of work. Could you say more?

olafurpg 5y ago
I'm an engineer on the code intel team at Sourcegraph. You can try out compiler-accurate code navigation here https://sourcegraph.com/github.com/sourcegraph/sourcegraph@24798dbdf7a36b63475571e291831ef8b507fd1c/-/blob/lib/codeintel/lsif/conversion/errors.go?L15:35#tab=references https://sourcegraph.com/github.com/sourcegraph/sourcegraph@2... See "Go to definition" and "Find references". The general idea is that you should be able to navigate your codebase online with Sourcegraph similar to how you would navigate the code with a local IDE (IntelliJ, VS Code). The benefits of Sourcegraph become more pronounced once the size of the codebase grows, especially across multiple repositories, and you're working with a large team of developers.

deleted 5y ago

[deleted]

mrkramer 5y ago

I wouldn't be surprised if Google acquires this at this point.

sqs 5y ago
We're going to remain an independent company, not be acquired. We've got a strong underlying business and tons of future growth (code search has very low penetration today, and we're working hard to change that). If Google acquired us, would you be more or less likely to use Sourcegraph? If Google had a competing product, would you trust it more or less than our product (assuming all else is equal)? I believe the answers to both questions point to Sourcegraph being most valuable as an independent company. :)