With Google Chrome 2.0 comes extensions.
My very favorite firefox extension is firebug. It’s the one I really couldn’t live without. It’d be like trying to mountain climb with only only twenty feet of rope. Painful and unnecessary.
Chrome is the up and comer with excellent performance and seamless google integration. What would it take for me to dump my tried and true mozilla browser for the new kid on the block? At the very minimum a ported or trumped firebug equivalent.
If firebug were a commercial product I imagine there would be much more of a chance for a straight port. I’m sure the revenue generating (directly or indirectly) toolbars will get ported with ease. But firebug? Maybe what’s more likely is a firebug inspired chrome specific extension. If that happens it’ll either fall short or kick firebugs ass.
I’m sure I’m not the only web developer that feels this way. While we may not make up a significant market share in terms of raw numbers it’s because we bit twiddlers are constantly remaking the internet that I think this is an important hurdle for chrome to overcome in it’s quest for world domination relevancy. Like the human body the internet completely regenerates itself every seven years or so, and it’s we web monkeys, not the voodoo super magic of biology that is responsible for this evolution one Console/DOM/Debugger/Cookie/Net panel use at a time.
From a platform development perspective it’s a fairly cut and dry real world test. Will Chrome pass the firebug challenge? Maybe by the time you read this they have already. Maybe not.
have you tried chrome yet? Most of firebug’s functionality is built-in under the developer options. You can view the generated html rather than just the source, write arbitrary code to the page, and analyze the network activity
I do a lot of page profiling to hunt down rendering problems and bad javascript, and the only extension things that keep me on firefox are foxyproxy’s regex support (which is insanely great) and flash tracer (which if I wasn’t lazy I could replace with a log tail or something)
Yea I’ve seen the element inspector and console, it’s handy but not quite as useful as a fully equipped firebug.
If they keep building it out native in the browser like that it could catch up pretty quick though.
The current dev build 4.0.xxxx has a set of developer tools. I knew about the inspect elements stuff before but without the “Net” panel it wasn’t good enough. But there is now a resources panel that seems to be working pretty well. I’ve been using the Dev build for a week and it seems pretty stable. I just finally set my default browser to chrome – now it’s my dev browser too!