Hacker News new | past | comments | ask | show | jobs | submit login

A proper debugger like the one in VS and general structured logging would like to challenge that statement. I'll take those over what you have in the web space any day.



What are the criteria that define whether a debugger is 'proper' or not?


There are many, but for my line of work:

* Conditional Breakpoints

* Function breakpoints to add ad-hoc logging

* Show type information

* Ability to custom render state, a graph for instance.

* GUI to browse the state

* CLI to query the state

* Ability to alter state

* Multithread debugging support

* Record execution history and state so you can debug after the fact for hard non reproducible bugs.

* Remote debugging

* Support for network traffic debugging


Thanks for this list and I'm full agreement.

Chrome developer tools will do all of these except

> * Record execution history and state so you can debug after the fact for hard non reproducible bugs.

^ Which would frankly be awesome. Various libraries provide their own userland support for this but it's all fragmented with hugely varying levels of quality and flexibility, but out of the box support would make me so happy (unless this already exists in which case, someone please enlighten me!).




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: