IE9 debugger.....how bad is that!
-
After having spent some time in the Chrome debugger recently, I thought I would have a quick look into IE9's. I generally do not use IE for anything other than work webmail with OWA, So have had no reason to poke into it's debugger. I thought I would start by seeing how it was at CSS manipulation. Nothing complicated, just view and change the "Welcome" text on CodeProject homepage to Red with a Green background. The whole experience was clunky compared to Chrome. It took almost 5 seconds from hitting enter before the page updated with the new color value! (Chrome is instant in comparison). As for javascript manipulation, again clunky, and more steps needed to do the same thing. Safe to say, i'm keeping clear of IE9 debugger thank-you very much.
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
It is a vast improvement over IE8, and I don't think it was even there for IE<8. Unfortunately I use it quite a bit.
Curvature of the Mind now with 3D
-
After having spent some time in the Chrome debugger recently, I thought I would have a quick look into IE9's. I generally do not use IE for anything other than work webmail with OWA, So have had no reason to poke into it's debugger. I thought I would start by seeing how it was at CSS manipulation. Nothing complicated, just view and change the "Welcome" text on CodeProject homepage to Red with a Green background. The whole experience was clunky compared to Chrome. It took almost 5 seconds from hitting enter before the page updated with the new color value! (Chrome is instant in comparison). As for javascript manipulation, again clunky, and more steps needed to do the same thing. Safe to say, i'm keeping clear of IE9 debugger thank-you very much.
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
Even though I'm a Chrome guy, I do find IE9's debugger useful at times, particularly when debugging scripts. The step-through/breakpoint stuff, complete with locals, watches, etc. is better than Chrome's tools. Also, the fact that I can break automatically when a script error occurs is also superior to Chrome. That said, for a quick check of "what's the status of this JavaScript value?", Chrome works just fine, and is quicker to get a result than IE9.
My Messianic Jewish blog: Kineti L'Tziyon My software blog: Debugger.Break() Judah Himango
-
Even though I'm a Chrome guy, I do find IE9's debugger useful at times, particularly when debugging scripts. The step-through/breakpoint stuff, complete with locals, watches, etc. is better than Chrome's tools. Also, the fact that I can break automatically when a script error occurs is also superior to Chrome. That said, for a quick check of "what's the status of this JavaScript value?", Chrome works just fine, and is quicker to get a result than IE9.
My Messianic Jewish blog: Kineti L'Tziyon My software blog: Debugger.Break() Judah Himango
All of that can be done with Chrome. Pause on Exceptions Beginner Guide to Page and Script Debugging with Chrome (article by the OP)
Somebody in an online forum wrote:
INTJs never really joke. They make a point. The joke is just a gift wrapper.
-
Even though I'm a Chrome guy, I do find IE9's debugger useful at times, particularly when debugging scripts. The step-through/breakpoint stuff, complete with locals, watches, etc. is better than Chrome's tools. Also, the fact that I can break automatically when a script error occurs is also superior to Chrome. That said, for a quick check of "what's the status of this JavaScript value?", Chrome works just fine, and is quicker to get a result than IE9.
My Messianic Jewish blog: Kineti L'Tziyon My software blog: Debugger.Break() Judah Himango
Judah Himango wrote:
Also, the fact that I can break automatically when a script error occurs is also superior to Chrome
In Chrome, on the Scripts view, at the bottom the Pause can be set in one of three modes; 1) Don't pause on Exceptions 2) Pause on uncaught exceptions 3) Pause on all exceptions. That should mean that the scenario you mention is catered for in either mode 2 or 3.
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
-
All of that can be done with Chrome. Pause on Exceptions Beginner Guide to Page and Script Debugging with Chrome (article by the OP)
Somebody in an online forum wrote:
INTJs never really joke. They make a point. The joke is just a gift wrapper.
I didn't say Chrome couldn't do that, I said the experience was quite a bit better with IE9. YMMV.
My Messianic Jewish blog: Kineti L'Tziyon My software blog: Debugger.Break() Judah Himango
-
Judah Himango wrote:
Also, the fact that I can break automatically when a script error occurs is also superior to Chrome
In Chrome, on the Scripts view, at the bottom the Pause can be set in one of three modes; 1) Don't pause on Exceptions 2) Pause on uncaught exceptions 3) Pause on all exceptions. That should mean that the scenario you mention is catered for in either mode 2 or 3.
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
Cool, this I didn't know. Still, the debugging experience just "feels" better in IE9. I don't know why, exactly, but when I'm doing heavy debugging, I feel more in control with IE9. I don't think it's just bias, considering I've been running Chrome as my main browser for years now.
My Messianic Jewish blog: Kineti L'Tziyon My software blog: Debugger.Break() Judah Himango
-
Cool, this I didn't know. Still, the debugging experience just "feels" better in IE9. I don't know why, exactly, but when I'm doing heavy debugging, I feel more in control with IE9. I don't think it's just bias, considering I've been running Chrome as my main browser for years now.
My Messianic Jewish blog: Kineti L'Tziyon My software blog: Debugger.Break() Judah Himango
My guess is it doesn't feel right unless there are little red spheres. Rounded blue arrows? What kind of lame ass debug symbol is that! :-D
Curvature of the Mind now with 3D
-
My guess is it doesn't feel right unless there are little red spheres. Rounded blue arrows? What kind of lame ass debug symbol is that! :-D
Curvature of the Mind now with 3D
Ha, +5.
My Messianic Jewish blog: Kineti L'Tziyon My software blog: Debugger.Break() Judah Himango
-
Ha, +5.
My Messianic Jewish blog: Kineti L'Tziyon My software blog: Debugger.Break() Judah Himango
Eh depends on what I am doing, if it's just general screw around with some CSS stuff or check a value then yeah chrome, a bit faster. When I am drilling into sub arrays in my javascript to yank out / manipulate values, while cross referencing them to my back end values, IE9 a bit nicer. Also I use IE9 along with Visual Studio a bunch as it provides much greater detail than firebug and chrome do. Yes it's all about product tie in but hey it's superior cause of it, and doesn't cost me anything else. Granted I'm a .net programmer so it makes more sense to use debuggers built to handle the MS stack in more detail. So call it bias to some degree, but overall chrome (which I use very often for its fast debugger) does fail short on a bunch of things that IE9 debugger does wonderfully.
-
After having spent some time in the Chrome debugger recently, I thought I would have a quick look into IE9's. I generally do not use IE for anything other than work webmail with OWA, So have had no reason to poke into it's debugger. I thought I would start by seeing how it was at CSS manipulation. Nothing complicated, just view and change the "Welcome" text on CodeProject homepage to Red with a Green background. The whole experience was clunky compared to Chrome. It took almost 5 seconds from hitting enter before the page updated with the new color value! (Chrome is instant in comparison). As for javascript manipulation, again clunky, and more steps needed to do the same thing. Safe to say, i'm keeping clear of IE9 debugger thank-you very much.
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
I'd say Firebug is still the best tool out there for debugging CSS and scripts. I think the Firebug creator recently joined Google to work on devtools for Chrome, so there might be great improvements for those in the future!
-
Even though I'm a Chrome guy, I do find IE9's debugger useful at times, particularly when debugging scripts. The step-through/breakpoint stuff, complete with locals, watches, etc. is better than Chrome's tools. Also, the fact that I can break automatically when a script error occurs is also superior to Chrome. That said, for a quick check of "what's the status of this JavaScript value?", Chrome works just fine, and is quicker to get a result than IE9.
My Messianic Jewish blog: Kineti L'Tziyon My software blog: Debugger.Break() Judah Himango
I find FireBug for firefox, better than the two. Don't see a reason to change
"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson