New ask Hacker News story: Ask HN: DDD was a great debugger – what would a modern equivalent look like?
Ask HN: DDD was a great debugger – what would a modern equivalent look like?
10 by manux81 | 5 comments on Hacker News.
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.
10 by manux81 | 5 comments on Hacker News.
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.
Comments
Post a Comment