2 ms·
I agree (somewhat) that print debugging shouldn't be praised over interactive debugging, but when you write a revolutionary new debugger like rr, please please
by flohofwoe 6y ago
I agree (somewhat) that print debugging shouldn't be praised over interactive debugging, but when you write a revolutionary new debugger like rr, please please build a good UI workflow first, and make it work at least on Windows and macOS too.
For instance, from a "time travelling debugger" I would expect some sort of graphical time line view, where I can immediately see where on the timeline I am currently, and jump back and forth while inspecting program state and memory in UI panels.
A good UI is the most important part of a debugger, and the area with the most potential for improvement (Visual Studio is generally praised as the best debugger around, but when you think about it, the UI is archaic, yet it's the best we have).
Without a good debugging UI and intuitive workflows, it's no wonder people are falling back to printf-debugging.