Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
beyang
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
by
beyang
4y ago
Sourcegraph : FishEye :: Google + Chrome : Alta Vista + IE5
32.
▲
by
beyang
4y ago
We have that! https://sourcegraph.com/github.com/golang/go/-/blob/src/net/... * Works cross-repositories, over our indexed corpus of 6M OSS repositories, or your private code * Multi-langu
33.
▲
by
beyang
4y ago
Updated link: https://twitter.com/sourcegraph/status/1577420437671190528?s...
34.
▲
by
beyang
4y ago
^ Link is broken, but the Twitter Live is still happening at the designated time (tomorrow, Wednesday, 1pm PT)
35.
▲
by
beyang
4y ago
Hmm, I think we might need to update that ticket. 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
36.
▲
by
beyang
4y ago
Bazel support in what sense? We have basic code nav across every major language, select precise indexers known to work with Bazel (with some degree of work), and we have improved code nav for Bazel files themselves ( https://githu
37.
▲
by
beyang
4y ago
LSP has addressed the editor code nav problem, but not the "just works in my web browser across all my code and multiple revisions" problem or the "let me build on top of a structured representation of code to enhance all my
38.
▲
by
beyang
4y ago
* Full code intelligence platform (not just code search) with Code Insights for tracking trends ( https://about.sourcegraph.com/code-insights ) and Batch Changes for large-scale refactors ( https://about.sourcegraph
39.
▲
by
beyang
4y ago
Sourcegraph's licensing is open core (similar to GitLab): https://handbook.sourcegraph.com/departments/engineering/pro... . Our code is public, regardless of whether it is open-source or enterprise licensed. T
40.
▲
by
beyang
4y ago
Sourcegraph CTO here. We're elated to welcome Steve to the team and will be hosting a Twitter live / AMA ( https://twitter.com/sourcegraph/status/1577364344056201236 ) with him tomorrow at 1pm PT. Join us
41.
▲
How TypeScript ESLint works, a deep dive into the source
(sourcegraph.com)
1 points
by
beyang
4y ago
|
0 comments
42.
▲
by
beyang
4y ago
We're trying out a series at Sourcegraph doing walkthroughs and deep-dives into popular open-source projects: 1. How Caddy web server works: https://sourcegraph.com/notebooks/Tm90ZWJvb2s6MTM2Nw== 2. How TypeScript
43.
▲
by
beyang
4y ago
Author of the post here. Thought it might be of interest to call out some observations about how the world has changed since I wrote this: 1. Code search is more mainstream. It used to be most of Sourcegraph's sales came from ex-Google
44.
▲
by
beyang
4y ago
Ironically, some of the steps that Bazel takes to make builds hermetic make it more difficult to integrate with to pull the information we need out of the build for precise code navigation. But we're working on it :) If this is an area
45.
▲
Sourcegraph now indexes all 87k+ Rust Crates
(twitter.com)
1 points
by
beyang
4y ago
|
0 comments
46.
▲
Deep dive into Caddy web server
(sourcegraph.com)
7 points
by
beyang
4y ago
|
0 comments
47.
▲
by
beyang
4y ago
Similar concept: https://news.ycombinator.com/item?id=31948833
48.
▲
QBE Notes
(wiki.alopex.li)
2 points
by
beyang
4y ago
|
0 comments
49.
▲
I interviewed Max Howell, the creator of Homebrew
(about.sourcegraph.com)
10 points
by
beyang
4y ago
|
9 comments
50.
▲
by
beyang
4y ago
Author of the post here. This really resonates with me. One of the best pieces of advice I've received in my life as a programmer, from my first manager actually, was "focus on getting an end-to-end system up and running first,
51.
▲
by
beyang
4y ago
Sourcegraph CTO (and author of the post) here. There's no part of our product that seeks to track software productivity? We do have a feature ( https://about.sourcegraph.com/code-insights ) built around code search that
52.
▲
by
beyang
5y ago
Sourcegraph CTO here. It's interesting to read about GitHub's approach and how it contrasts with the approach we've taken at Sourcegraph. One of the key tradeoffs the article highlights is GitHub's decision to take the &