DDD was a great debugger – what would a modern equivalent look like today?

3 pointsby manux813 hours ago1 comment

chrsw3 hours ago
Something like this maybe:
https://whitebox.systems/
Doesn't seem to meet all your desired features though.
- manux812 hours ago
  Yes, that’s a good example — thanks for the link. Tools like this seem very strong at visualizing and exploring state, but they still tend to stay fairly close to the traditional “pause and inspect” model. What I keep struggling with is understanding how a particular state came to be — especially with concurrency or events that happened much earlier. That gap between state visualization and causality feels hard to bridge, and I’m not sure what the right abstraction should be yet.
  - chrsw2 hours ago
    Here's another one
    https://scrutinydebugger.com/
    It's for embedded systems though, which is where I come from. In embedded we have this concept called instruction trace where every instruction executed with the target gets sent over to the host. The host can reconstruct part of what's been going on in the target system. But there's usually so much data, I've always assumed a live view is kind of impractical and only used it for offline debugging. But maybe that's not a correct assumption. I would love to see better observability in embedded systems.