This seems like it’s positioned for a very specific use case, understanding obfuscated code. But it seems like the same capabilities could be exceedingly useful

This seems like it’s positioned for a very specific use case, understanding obfuscated code. But it seems like the same capabilities could be exceedingly useful for a lot of more mundane code analysis tasks. Determining actual code paths accessed and possible types at runtime in JS is challenging even if you manually provide a lot of that information to eg TypeScript. Getting even confirmation of a subset of that information and additional insight into the dynamic superset from real runtime JIT analysis could be invaluable for understanding a codebase if it’s inscrutable, and even for designing static optimization tooling.