If I played the old one and enjoyed it, what's the pitch for the new one? e.g. why is it better? On the surface it kinda just looks like the previous one, but I haven't dug into it
Unfortunately GPUs (and even CPUs' SIMD) floating point math is riddled with cross-platform determinism issues; hardware manufacturers intentionally trade that in order to get faster math operations in general, because although behavior of floating point is defined in IEEE 754, you get rounding errors for each operation.
Compiler optimizations (and remember, GPU drivers each use their own compiler behind the scenes to translate to their actual hardware architecture) can alter rounding errors of each operation, and parallel execution - which differs from hardware to hardware - also affects it.
Some APIs (Cuda?) let you disable all optimizations and there are ways to get cross-platform determinism, but in general it's much much slower if you want bit-for-bit equality across different hardware.
SPIR-V/Vulkan for example[0] only define an error range based in ULP for some operations - not bit-for-bit equality.
I used to have coworkers ask 'what programmers do you look up to?', and that question always felt icky to me because it kind of implied you can't make the same choices and become your own hero.
Over time, I found people whose life choices and personal advice I deeply appreciate. Andrew is definitely one; partly because of overlapping software goals, but mainly because of just how human & approachable he is. Genuinely just a great guy who wants others to succeed and share in his successes in life.
This is pretty much exactly what we've built at Sourcegraph. Microsoft had introduced (but pretty much abandoned before it even started) LSIF, a static index format for LSP servers which encodes in detail all possible LSP requests/responses, effectively.
We took that torch and carried it forward, building the spiritual successor called SCIP[0]. It's language agnostic, we have indexers for quite a few languages already, and we genuinely intend for it to be vendor neutral / a proper OSS project[1].
In the top right corner of the tooltip it will say either "Search-based" or "Precise" - in this case, you're right, we don't have the abseil-cpp repo indexed so it falls back to search-based as you describe.
We do have a C++ code indexer in beta, https://github.com/sourcegraph/lsif-clang - it is based on clang but C++ indexing is notably harder to do automatically/without-setup due to the varying build systems that need to be understood in order to invoke the compiler.
FWIW Sourcegraph has fully precise/semantic go-to-definition, find-references, etc. We use SCIP code indexers (a spiritual successor to LSIF, the Microsoft standard for indexing LSP servers)
Really putting the router in an aluminum enclosure/Faraday cage if you can is the only way to prevent this. Then just use the lan ports on the device, but also make sure the LAN cables are shielded because it could be using them as antennas given how compromised wifi router firmwares usually are.
In GitHub's case, only if you're willing to pay for the bandwidth... something which I am currently struggling with in regards to open source projects needing binaries in-repo..