Future of JavaScript Debugging: Dbux and Dynamic Program Analysis
summary
Debugging consumes 30–60% of developer time, and Dbux is a VS Code extension that records runtime traces and visualizes them as a searchable call graph and dynamic slicing view. It shows per-call inputs/outputs, async call relationships, recursion trees (fibonacci demo) and a timeline-based map so backward reasoning and eliminating irrelevant code become fast. The demo works on JavaScript web examples (ToDo MVC); React Native and native Java/Kotlin are not supported out of the box.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:41Outline
- 2:56How do we usually debug?
- 3:36What is debugging really?
- 4:39How do devs locate their bugs?
- 5:47The "dark matter" of debugging
- 6:57My opinion: We lack a "debugging culture"
- 8:30What is a debugger?
- 9:46What is a "good interactive debugger"?
- 10:57How does an interactive debugger work?
- 15:29Dynamic analysis example
- 23:22What is dynamic analysis?
- 39:05Interactive debugging features
- 44:02An important survey on interactive debugging
- 44:55Q&A
related talks
33mEssential JavaScript debugging tools for the modern detective
34mVisualising program execution
29mEssential JavaScript debugging tools for the modern detective
23mDebugging the Web
53mBeyond console.log
28mEssential JS debugging tools for the modern detective
15mThe JavaScript Debug Robot
49mEffective Browser JavaScript Debugging
