DDD 是一个很棒的调试工具——那么现代的同类工具会是什么样子呢？
我一直认为，DDD在当时是一个令人惊讶的优秀调试工具。它让程序执行变得可视化：堆栈、数据和控制流都能同时呈现。你可以真正“看到”程序在做什么。
与此同时，它显然是一个不同年代的产物：
- 单进程
- 主要是同步代码
- 没有真正的并发或异步概念
- 过时的用户界面和交互模型
今天我们调试的系统截然不同：多线程代码、异步运行时、长时间运行的服务、分布式组件。然而，大多数调试器在概念上仍然与GDB + 单步调试相似，只是包装在一个更美观的用户界面中。
我很好奇其他人对此的看法：
- DDD（或类似旧工具）中有哪些理念仍然有价值？
- “现代DDD”需要如何处理今天的软件？
- 你认为交互式调试仍然是正确的抽象方式吗？
我主要是从设计的角度提问——我自己也在尝试一些调试器的想法，但我更感兴趣的是听听经验丰富的工程师们今天如何看待这个问题。
查看原文
I’ve always thought that DDD was a surprisingly good debugger for its time.
It made program execution feel visible: stacks, data, and control flow were all there at once. You could really “see” what the program was doing.
At the same time, it’s clearly a product of a different era:
– single-process
– mostly synchronous code
– no real notion of concurrency or async
– dated UI and interaction model
Today we debug very different systems: multithreaded code, async runtimes, long-running services, distributed components.
Yet most debuggers still feel conceptually close to GDB + stepping, just wrapped in a nicer UI.
I’m curious how others think about this:
– what ideas from DDD (or similar old tools) are still valuable?
– what would a “modern DDD” need to handle today’s software?
– do you think interactive debugging is still the right abstraction at all?
I’m asking mostly from a design perspective — I’ve been experimenting with some debugger ideas myself, but I’m much more interested in hearing how experienced engineers see this problem today.