firebug
chrome is a million times better than firefox (with firebug) for development, and firefox (with firebug) is a million times better than ie is for development.
use chrome and open the developer tools then you can view all of the sources and step through them line by line and see all of the values.
I agree with this statement.
Chrome's developer tools are amazing. Very fast, well integrated, and they are powerful.
Firebug has most of the same functionality, but my experience is that it is slower, sometimes buggier, and it would sometimes cause pages to crash.
IE's tools are ok, but really not as good as firebug.
The only problem I have with Chrome is they do not allow you to view and edit the requests and responses being sent. There is a addon for Firefox that allows that and Chrome itself doesn't give any access to it.
you can view the requests/responses no problem in chrome. as for editing them though i don't know anything about that so you are probably correct there. you could probably put a breakpoint before the request is being made though and just change the data right before the call that hits your backend.
The amount of times I've been in a situation where I needed to view the request and response data was two, so it isn't a huge deal. But, it is just something that isn't available for some reason on Chrome. The intentionally block addons from having access to that information. I suppose it makes sense from a security standpoint, but when I am developing, I don't care about the average Joe needing his hand held.
I don't get it. You can pretty easily view the responses being sent, it is the Network tab. It give you everything that is being sent from everywhere (including add ons).
Editing is a different problem. You can edit live data, css, and html in chrome. If you want to manipulate the data, throw down a breakpoint and do it. The only thing you really can't do is edit the data directly from the network tab, but I've never really ran into a situation where that was something I really REALLY wanted to do.
The amount of times I've been in a situation where I needed to view the request and response data was two, so it isn't a huge deal. But, it is just something that isn't available for some reason on Chrome. The intentionally block addons from having access to that information. I suppose it makes sense from a security standpoint, but when I am developing, I don't care about the average Joe needing his hand held.
Decided to go with Webstorm. For whatever reason, I dislike using Chrome's console for debugging.
if you are trying to use the console for debugging, you're doing it wrong heh.
they have a built in debugger, just view the sources tab and put breakpoints in the sources that you want to break on.
not sure what webstorm is though so i can't comment on that.
you can view the request/response data in chrome no problem. just click the network tab and find the request and you can view both of them.
EDIT:
oh i just read your other response. if that is the case, get the chrome addon postman. it's very easy to use and lets you send whatever requests you want to whatever endpoints, and view the responses.
https://chrome.google.com/webstore/detail/postman-rest-client/fdmmgilgnpjigdojojpjoooidkmcomcm?hl=en
Must be pretty new then (past 2-3 years). I found the tool I needed when I needed it. Haven't needed it either. I've been using Chrome a long time and don't plan on changing. I remember when using extensions required adding them as arguments to the executable path. =(