Hacker News new | ask | show | jobs
by masklinn 5720 days ago
* The Webkit Developer Tools (Safari, Chrome) are roughly on-par. They progress faster and have some features Firebug doesn't, but they don't have plugins and there are some nice features of Firebug they don't replicate (built-in introspection of jquery collections). They're way fucking faster than Firefox with Firebug enabled though, that's a big plus. They also implement most of the Firebug `console` API. The only tool which is not as good as Firebug's would be the DOM inspector, as it's a bit harder to edit nodes in line (though it's not actually hard).

* IE8's developer tools are a start, but they're slow, buggy and tend to crash a lot (either a soft-crash where some features suddenly stop working, or a hard crash where the inspector takes down the browser). I think they only implement `console.log`, and it only works when you have the tools open otherwise it generates an error

* Opera's Dragonfly... well I haven't tried it in a long time, though I mean to do it soon-ish: during last week's Opera "AMA" on reddit I was told good progress had been made.

These days I use Safari as my main development browser, and it's very enjoyable.

edit: addendum, there are also things simply done differently. For instance Firebug displays the ajax requests in the console, which is something I find spammy but you may like. On the other hand the Webkit dev tools not only have a dedicated console tab but you can access a JS console from any tool (by pressing [ESC] in Safari, don't know the chrome shortcut, might be the same, it will slide up a console to half-height in the manner of e.g. OSX's Visor) which is very handy, especially in the debugger.