1. Overview
  2. Debugging and CI
  3. Other workflows
  4. Debugging as a service
  5. Basic interface
  6. Call stacks
  7. Explaining dataflow
  8. Multiprocess
  9. Search box
  10. Source files
  11. Condition and print expressions
  12. Toolbox
  13. Alerts
  14. Application logs
  15. Callees
  16. View operators
  17. Notebook
  18. Instruction execution
  19. Browser UI integration
  20. Additional views
  21. GDB
  22. System debug info
  23. Compiler issues
  24. Future work
  25. Related work
  26. Conclusions

Conclusions

Pernosco shows that debuggers can be vastly more powerful than what people have today. Just as importantly, we have shown we can integrate debugging into developer workflows where debugging is currently infeasible. Yet there is still a lot more potential for improving the debugging experience further, to make developers even more efficient and happy. Expectations and hopes for improved debugging tools should be much higher than they currently are.

For Pernosco itself, a key question is whether our workflow integrations are enough for developers to use Pernosco for the majority of their debugging. Another key question is whether Pernosco is good enough to overcome the formidable barrier of developer inertia. Perhaps the most important question of all is whether we can overcome the cultural expectation that debuggers are free. We shall see.

<< Related work