4 ms·

Glad they finally gave the Dev tools an update in IE11. It's a welcome thing for those that still need to support users running IE.

by wluu 13y ago

harrytuttle 13y ago
I'm using IE11 on windows 8.1 to prep our product for it. The developer tools are a piece of shit still. The JavaScript debugger is hideous, it's clunky as hell and actually changes the page behaviour resulting in all sorts of impossible heisenbugs.
- k3n 13y ago
  I haven't used the IE11 version yet (still on IE9 for work development), but IE9's are pretty solid. Perhaps I'm suffering from a sort of perverted Stockholm syndrome, but they work well for me. They're not without annoyances (like having to refresh once you enable debugging), but once you get past those it works as expected. Chrome's are also very nice, but at the same time, often overblown for my needs. For what it's worth, I mainly debug minor performance issues (99.9% relating to abusing the DOM) and the odd bugs in our own software. So, while the GPU and heap profiling and whatnot are grand, for my job YAGNI at all. And I'll probably get drawn & quartered for this, but Firebug just plain sucked the last time I tried to use it (a month or 2 ago). I can only guess that it's because it's still an add-on, and not native, but it just felt slow and clunky, and like it was all held together with bailing wire and duct tape (which, considering it's an add-on, might not be far from the truth). It's ironic because I was an early-adopter of Firebug back when it was first introduced, and it set the early standard of just how awesome in-browser debugging tools could be, but now I avoid it. I do have big hopes for Mozilla's remake of the native dev tools though, I feel it's been a long time coming.
  - drivebyacct2 13y ago
    Does opening the debugger still patch in console.log and then keep it patched in even after you disable the debugger, leaving you to track down impossible to find bugs because it stops all execution on the page and somehow suppresses the error that console.log isn't actually available anymore? Yeah, I'm with the other angry devs in this thread, IE can continue to jump off a bridge.
  - Shorel 13y ago
    Opera's Dragonfly is still one of the best for JS debugging. It's sad it's going to die with Presto.

Glad they finally gave the Dev tools an update in IE11. It's a welcome thing for those that still need to support users running IE.

by wluu 13y ago

Glad they finally gave the Dev tools an update in IE11. It's a welcome thing for those that still need to support users running IE.

harrytuttle 13y ago

I'm using IE11 on windows 8.1 to prep our product for it. The developer tools are a piece of shit still. The JavaScript debugger is hideous, it's clunky as hell and actually changes the page behaviour resulting in all sorts of impossible heisenbugs.

k3n 13y ago
I haven't used the IE11 version yet (still on IE9 for work development), but IE9's are pretty solid. Perhaps I'm suffering from a sort of perverted Stockholm syndrome, but they work well for me. They're not without annoyances (like having to refresh once you enable debugging), but once you get past those it works as expected. Chrome's are also very nice, but at the same time, often overblown for my needs. For what it's worth, I mainly debug minor performance issues (99.9% relating to abusing the DOM) and the odd bugs in our own software. So, while the GPU and heap profiling and whatnot are grand, for my job YAGNI at all. And I'll probably get drawn & quartered for this, but Firebug just plain sucked the last time I tried to use it (a month or 2 ago). I can only guess that it's because it's still an add-on, and not native, but it just felt slow and clunky, and like it was all held together with bailing wire and duct tape (which, considering it's an add-on, might not be far from the truth). It's ironic because I was an early-adopter of Firebug back when it was first introduced, and it set the early standard of just how awesome in-browser debugging tools could be, but now I avoid it. I do have big hopes for Mozilla's remake of the native dev tools though, I feel it's been a long time coming.
- drivebyacct2 13y ago
  Does opening the debugger still patch in console.log and then keep it patched in even after you disable the debugger, leaving you to track down impossible to find bugs because it stops all execution on the page and somehow suppresses the error that console.log isn't actually available anymore? Yeah, I'm with the other angry devs in this thread, IE can continue to jump off a bridge.
- Shorel 13y ago
  Opera's Dragonfly is still one of the best for JS debugging. It's sad it's going to die with Presto.