> - display JavaScript data structures in more visual way
Sort of? Is the existence of the 'inspect' function enough?
> - breakpoints on DOM changes, events and Ajax requests
I'm not sure about this. I mean, you can set the breakpoints in code per usual but I expect you mean setting them on the nodes themselves and perhaps global breakpoints in the net panel?
> - debugger API to work together with IDEs like Netbeans
It's possible with the remote debugging protocol but the only implementation I know of is the proof of concept that Paul Rouget put together two years ago, although I don't think he released any code.
As I mentioned, this goes back to approximately three years ago.
The developer tools console could do:
- completion while typing
- display JavaScript data structures in more visual way
- breakpoints on DOM changes, events and Ajax requests
- profile network, memory and cpu usage
- navigate cookies, indexdb and websql databases
- reformat JavaScript code
- CSS editor
- work as IDE
- debugger API to work together with IDEs like Netbeans
- profile 2D and 3D performance
Basically, even though I prefer native to web, while using Chrome Developer Tools I had the feeling I was kind of back to Smalltalk.
Additionally their website was better than MDN in terms of information, specially thanks to the many sessions on Google conferences.
https://developer.chrome.com/devtools
That said, maybe Firefox is now on par.