val-town-mirror
stack-graphs
| val-town-mirror | stack-graphs | |
|---|---|---|
| 2 | 6 | |
| 3 | 702 | |
| - | 2.1% | |
| 9.9 | 9.5 | |
| 14 days ago | 10 days ago | |
| TypeScript | Rust | |
| - | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
val-town-mirror
-
Code Search Is Hard
Well this is fun...
git clone https://github.com/pomdtr/val-town-mirror
stack-graphs
-
Code Search Is Hard
https://github.com/pyjarrett/septum
The hardest part about getting code search right imo is grabbing the right amount of surrounding context, which septum is aimed at solving on a per-file basis.
Another one I'm surprised hasn't been mentioned is stack-graphs (https://github.com/github/stack-graphs), which tries to incrementally resolve symbolic relationships across the whole codebase. It powers github's cross-file precise indexing and conceptually makes a lot of sense, though I've struggled to get the open source version to work
-
Even the Pylint codebase uses Ruff
[2]: https://github.com/github/stack-graphs
-
The technology behind GitHub’s new code search
> It doesn't have the faintest idea where the name is defined, or if there's even a difference between a function name, a parameter name, or a word in a comment.
I don't think what you are saying is actually true for stack-graphs[0][1].
[0]: https://github.com/github/stack-graphs
[1]: https://github.blog/2021-12-09-introducing-stack-graphs/
-
Should I be worried or not worried about Tree-sitter now that the Atom editor has been killed?
I think GitHub still has some use for tree-sitter. In this post it's mentioned that their new code navigation system is based on tree-sitter. In a more recent post they welcome contributers to add special code navigation queries to existing languages. You can find their public repository here if you want to follow along with any developments. Since their code navigation system relies heavily on tree-sitter I don't think it's going anywhere soon (fingers crossed).
-
What happened with GitHub's semantic project?
Which they implement in Rust. https://github.com/github/stack-graphs
-
Stack Graphs
As mentioned elsewhere on this thread, stack graphs and Semantic were built by the same team (which I manage). Semantic is not abandoned, we've just been focusing on a different layer of our tech stack for the past year or so. https://news.ycombinator.com/item?id=29501389
That PR on the Semantic repo was our first attempt at implementing these ideas. We decided to reimplement it in a separate library (also open source, https://github.com/github/stack-graphs), which only builds on tree-sitter directly so that there's an easier story for us and language communities to add support for new languages. It's a fair point that we could have closed the Semantic PR to indicate that more clearly.
What are some alternatives?
semantic-source - Parsing, analyzing, and comparing source code across many languages
kickstart.nvim - A launch point for your personal nvim configuration
nvim-lspconfig - Quickstart configs for Nvim LSP
scip-zig - SCIP indexer for Zig!
pagefind - Static low-bandwidth search at scale
nvim-ts-context-commentstring - Neovim treesitter plugin for setting the commentstring based on the cursor location in a file.
lsif-clang - Language Server Indexing Format (LSIF) generator for C, C++ and Objective C
bar
nvim-treesitter-textobjects
enso - Hybrid visual and textual functional programming.
scip-clang
sourcegraph - Code AI platform with Code Search & Cody