I agree that must be true in an absolute sense, but part of the reason I'm making this is that I find visualization of internal program data to be valuable. I have other things I want to use this to help me build. But it's definitely a gamble whether I'll be able to convince many other developers that it's valuable :)

Thanks for the suggestion though. I do think it's interesting, but if I understand correctly, the volumes of data involved would require different sorts of visualization approaches, whereas I've spent lots of time specializing mine for high-level program state. For instance, the visualizations are specialized for common data structure types, and can be stepped backwards and forwards through, like in a stepping debugger. So if nothing else, I'd be very reluctant to pivot without really giving this a shot.

Let me know if I've missed anything about the kind of data you're thinking of—maybe it's more suitable than I think.