The similar acronym appears to be intentional:

> Note on the name: SCIP is pronounced the same way as “skip” and it’s a recursive acronym that stands for “SCIP Code Intelligence Protocol.”

> SCIP is also a purposeful nod to SICP (Structure and Interpretation of Programs), a book about analyzing programs.

https://sourcegraph.com/blog/announcing-scip#:~:text=SCIP%20...

Nor the other SCIP.

https://en.wikipedia.org/wiki/Secure_Communications_Interope...

Also not SCPI (Standard Commands for Programmable Instrumentation), widely used to control lab instruments and pronounced similarly ("skippy").

Also not this SCIP: https://www.scipopt.org/

There IS no… wait, wrong acronym.

... and not the solver for mixed integer (linear) programming (MI(L)P) and mixed integer nonlinear programming (MINLP):

> https://www.scipopt.org/

SCIP is a "nod" to SICP

I misread it too.

Imagine working for this company where engineers don’t know about SICP

I can’t speak for the Go bindings, but using the Rust crate has been pretty clean. Haven’t really felt the need to dip into deserializing raw .scip file in the time that I’ve been working with SCIP.

It looks like GitHub's tree-sitter powered code navigation is no longer maintained: https://github.com/github/stack-graphs

[dead]

In its simplest form, it's just a dump of the code intelligence information from a static copy of the code. This can power an LSP, however, without additional logic wouldn't be able to handle a project under edit, since the locations won't match between the indexed state and the edited project state; So it lends itself well for something like Sourcegraph that already displays a static copy of the codebase.

Uber uses SCIP as part of the LSP implementation for our Java monorepo (Pieces of which we've [open-sourced](https://github.com/uber/scip-lsp)). Standardizing on SCIP has helped us generalize tools to be independent of the compiler/language ecosystem (eg we could do call-stack-analysis on any project that exports valid SCIP; do feature flag cleanup; find refs/impls across a wider scope than most LSP servers can handle due to memory constraints).