The Future of SCIP
jdorfman
61 points
20 comments
March 27, 2026
Related Discussions
Found 5 related stories in 56.2ms across 3,663 title embeddings via pgvector HNSW
- Slop is not necessarily the future dakshgupta · 210 pts · March 31, 2026 · 49% similar
- SWE-CI: Evaluating Agent Capabilities in Maintaining Codebases via CI mpweiher · 114 pts · March 08, 2026 · 48% similar
- The future of version control c17r · 477 pts · March 22, 2026 · 45% similar
- Coding Agents Could Make Free Software Matter Again rogueleaderr · 141 pts · March 29, 2026 · 45% similar
- The future of code search is not regex – 100x faster than ripgrep neogoose · 14 pts · April 02, 2026 · 45% similar
Discussion Highlights (5 comments)
UncleOxidant
Oh, not SICP.
skybrian
The git repo is here: https://github.com/scip-code/scip Looks like it's defined using protocol buffers, with "rich Go and Rust bindings" and links to implementations for many other languages.
zingar
Something something powers go to definition… is this an implementation of an LSP server? Or a subset of what’s needed to implement LSP? A formerly proprietary alternative to LSP?
ananthakumaran
I have been using https://github.com/jacktasia/dumb-jump to quickly jump to definitions. LSP is hit or miss; in some languages, it works great, while in others, the implementation is not so good. I have been thinking about a middle ground based on Tree-sitter. GitHub uses Tree-sitter to power code navigation, but unfortunately, I can't find anything good that I can use offline. Why is there no ctags equivalent powered by Tree-sitter?
s20n
Structure and Computer of Interpretation Programs