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?
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), and we will probably experiment with more "AI-for-reading/understanding/maintaining code" stuff in the future.
Sourcegraph PM here. Both Scala and Cobol are supported out of the box through search-based code intelligence (https://srcgr.ph/3xDPYcs). We don't currently support RPG and PL/1. We also offer precise code intelligence (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), Java(https://srcgr.ph/3r7quBT), TS/JS(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.
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.
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. :)
10 comments
[ 3.0 ms ] story [ 32.8 ms ] threadHappy to answer any questions. If you've used Sourcegraph, please share what you liked and what needs to be better!
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?
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.
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. :)