The day that Chrome gets a Firebug tool...

[lkosak]

Hi check_ca,

I think what you may be missing is that people are using Firebug, with great success and very effectively, in ways that they cannot achieve in Chrome. I am one of these users, and it's the reason that despite an overwhelming desire to switch to Chrome as my primary development environment, I have to keep returning to Firefox.

When one is working with HTML/CSS/JS all day long, at a very fast pace, small things start to add up. I haven't seen the new iteration of Chromium you mention, but I doubt that even with this functionality, Chrome's developer environment is anywhere NEAR as robust as Firebug.

As a final note to everyone who is touting the idea that these Firebug advocates don't know what they want or need, I would recommend that you either spend enough time using Firebug to understand its unique virtues, or stop telling people that they don't know what they need. These are, in all likelihood, professional web developers; I'm guessing they know better than you do what they require of their tools.

-Lou

[yyrkoon]

Power users use an IDE with autocompletion, autoindentation and so on... A debugger is just useful to test some modifications (or to do profiling) but not to make an entire web page or a stylesheet

EDIT : on Chromium 4.0.286.0+, you can also edit HTML content exactly like in Firebug.

If you mean web developers, when referring to "power users", then you are mistaken. Web developers use, what web developer use.

Having been developing in several languages for close to 13 years now, I will say that developing in notepad++ has it's attractions. I do not need, nor want anything getting in my way. Such as auto complete, or auto indent. If I want something indented, I will indent it myself. How hard is it to press tab ? Having at one point really liking the Visual Studio code complete tool, at some point in time, since I had stopped using it in the last few years, it has become over cumbersome. Which now seems to get in my way more often than not.

Also. Just because something makes no sense to you (anyone really ), does not mean it wont make sense to someone else. As a couple of people have already stated; Chromes' element inspector is/was limited. That is not even mentioning that it can be buggy, and is visually laid out in a way that does not work for me personally. Not alone by far. I like many others need things to work well, and quickly for us. Otherwise the "tool" gets in our way, and slows us down. That can be a huge distraction sometimes, especially if you're creating something using multiple languages ( like interfacing a device through ajax etc ).

... and that is as they say . . . is just the tip of the iceberg.