oluwaseun_k

I tried to break the relay fallback because that is my job. Pulled the network out from under an active connection, switched between wifi and tethering, blocked the direct path at the firewall. It kept the stream alive every time, slower on relay but never dead. Operationally that resilience is worth more than the raw numbers. I would page someone over this far less often.

The benchmark numbers made me suspicious, so I ran it against the worst repository we own: a decade of C with generated code and three build systems fighting each other. It held up. Full index in a few minutes, queries back in well under a millisecond, and memory stayed flat enough that I would run it on a build agent without flinching.

What sold me was not the speed though. It was that the graph stayed correct after I rewrote a hot module and reindexed. Stale results are the usual failure mode for this kind of tool and I could not get it to lie to me.

My one reservation is the Hybrid LSP coverage. It is excellent for the listed languages, but our older Objective-C falls back to plain tree-sitter and you can feel the difference in type resolution. For anything modern, this is comfortably the fastest correct option I have tried.