Steve Yegge Joins as Head of Engineering of Sourcegraph(about.sourcegraph.com) |
Steve Yegge Joins as Head of Engineering of Sourcegraph(about.sourcegraph.com) |
Youngbloods: if you have not spent time with Steve Yegge's old writings, please go check them out. Much good received wisdom there.
1 Join a company
2 write a lengthy, self-important diatribe/novella about why he joined
3 Write several lengthy, self-important diatribes, often namedropping previous places he worked and/or how he accidentally influenced some C level officer just by dint of his unique persona =) That rascally Steve!
4 Repeat step 3 anywhere between 10-50 times
5 Quit job, write lengthy self-important diatribe about why he left (optionally leaping straight into step 1 again, sometimes with a break inbetween)
Should be an interesting 6 months for Sourcegraph, at least! Looking forward to seeing how this progresses.
If his presence and enthusiasm can get the compiler community aiming its collective brain power at real developer productivity problems (the why behind SourceGraph's exponential growth) rather than focused on compiler optimization problems, this is going to be a really great time to be writing software!
Like, I would frankly be surprised if we ever got more than one doubling out of Proebsting's law.
* Precise code navigation (vs. more fuzzy-level nav), powered by SCIP (spiritual successor to Grok, the system Steve built at Google)
* More powerful search language beyond regex (supports comby.dev) + user-friendly (smart search)
* Works across multiple GitHub instances + other code hosts (GitLab, Bitbucket, Perforce, enterprise Git repositories)
* Self-hosted deployment and enterprise scale
cs.github.com is a significant improvement over github.com/search—kudos to the team there!—but is about feature parity with something like OpenGrok, Hound, or Google Code Search before Steve built and integrated Grok (primarily cross-codebase regex search).
Rust Dependencies (crates.io) Python Dependencies (PyPI) Go Dependencies NPM Dependencies src.fedoraproject.org JVM Dependencies GitLab.com GitHub Public
and as of yesterday Savannah/GNU - https://github.com/sourcegraph/community/issues/38
More to come.
I want to have source intelligence but I can’t see the biggest chunk of my dev stack to be sourcegraph.
1) How can you write this whole article without saying "Kythe"?
2) How exactly can github search be as bad as it is? With all of Microsoft behind it, you'd think it would be a lot better than it is.
I'll be taking another look at Kythe, and reaching out to the current Grok team, as we expand scip. But ultimately it didn't matter what protocol/format we standardize on. We just need to standardize. So it's scip!
Well, it does discuss Grok (the closed source predecessor) extensively.
Finding a technology preview for a radically improved cross-language code search capability within GitHub was an unexpectedly nice surprise.
Interesting data point for the question: at what point in your career will you stop being asked to write code on a whiteboard to prove you aren't lying on your resume.
Many of us have faltered like this once or twice unless its an outright lie kind of situation.
Anyway, just sharing an anecdote and hope this works out well for all involved.
Oh cool - AFAICT, that "our code" link is a link to a demo instance of sourcegraph on sourcegraph's code. This looks like an interesting product.
And it's open source? What's present in the commercial offering that's missing from the open source one? Just support, or features too?
Our code is public, regardless of whether it is open-source or enterprise licensed. The open source code includes most of the product features; the enterprise code includes things like enterprise AuthN, AuthZ, and admin capabilities that are needed for large companies to use Sourcegraph.
Sourcegraph.com/search indexes over 6 million open-source libraries, nearly every github.com repository with at least 5 stars and the most popular projects across NPM, PyPI, Maven Central, and many more independent projects and code hosts.
https://source.chromium.org/chromium/chromium/src/+/main:v8/...
Click on the "ToBoolean" function, it brings up all call sites across all Chromium projects.
* Works cross-repositories, over our indexed corpus of 6M OSS repositories, or your private code * Multi-language (some projects at compiler accuracy, some at CTAGS-level accuracy)
His first set were from his time at Amazon: https://sites.google.com/site/steveyegge2/blog-rants
He then wrote a load of later ones when at Google: https://steve-yegge.blogspot.com/index.html
And, yes, the (in)famous platforms rant.
While the blogs range widely, a major overarching theme was static vs dynamic typing.
Basically everything he wrote is worth reading; and definitely a thousand times more that whatever's on the HN front page these days.
Check it here: http://steve-yegge.blogspot.com/2008/06/done-and-gets-things...
We're currently exploring what it means to support non-git VCSs natively in Sourcegraph, but we're not there yet.
https://sourcegraph.com/search?q=context:global+repo:%5Epyth...
Adding to my list: https://github.com/sourcegraph/community/issues/36
Until I see a more functional company with 100,000+ employees, I attribute all the issues to scale.
The idea is just a litmus test and I don’t think it’s useful for filtering anything other than liars. I never had someone completely freeze up.
Here's some docs on Bazel support for Java/Scala precise code nav: https://sourcegraph.github.io/scip-java/docs/getting-started.... Any languages you're looking for in particular?
So core code navigation functionality ought to work. There are some issues with different language features (macros, newer C++17 and C++20 features), as well as robustness (crashes on indexing certain code) but we're looking into bringing C++ support up to par with other languages.