Я dont't думают, существую общее правило, когда использовать язык сценариев. Языки сценариев легки, так разработайте, но иногда они тверды, делают обслуживание, особенно когда сценарий должен работать под различными платформами (операционные системы).
профессионалы языков сценариев, конечно:
Мятежники:
I would suggest starting with Firebug because it traditionally has provided the most powerful set of debugging features.
However IE dev tools (and others such as Opera Dragonfly) are rapidly catching up and are probably preferred if your pages are being displayed primarily in those browsers.
So I don't think you can get away with just learning one or the other. Find out which browsers your users prefer and install the developer tools for each browser.
You'll save yourself a lot of time solving obscure browser specific Javascript or DOM bugs using the debugging platform specific to that browser.
I would suggest Firebug first, as, it will help you determine errors more quickly, as I found it more intuitive to use, but, if you are only supporting IE then the IE Developer tools would be your best bet.
Which browsers do you support?
That will determine the best one to start with, but, if you have to, use Firebug for the initial debugging.
Learn both, at least if you are pro web coder. There's not much to learn anyway - it's just a tool.
You'll definitely feel at home with Firebug. I is the easiest and the most powerful of tools that I know of for debugging pages live. I constantly make use of it prior to committing a change to a CSS stylesheet (i.e. margins/paddings, colors and the like). The fact that it also includes a Javascript Debugger and a console is a plus. From what I gather, many that do not use Firefox use Firebug Lite. It's JavaScript powered and a bit slow, though.
IE8 Dev. Tools is useful, but the experience isn't very much alike Firebug, but the concept remains. I recommend also familiarizing yourself with Safari Web Inspector and Opera Dragonfly. They are debugging tools with similar aspects to Firebug.
Если это не для тестирования / отладки и причуд IE с JS, вам лучше придерживаться Firebug. IE8 DT даже близко не приближается к Firebug по производительности или удобству использования. Попробуйте IE8 DT и отладьте JS, пока вы запускаете проект в отладчике VS. Я избавлю вас от хлопот и скажу: «ВЫ НЕ МОЖЕТЕ». Разрабатывайте с Firefox в качестве стандарта, и 99% всего остального будет работать нормально.
As stated already, the answer is to learn both. As goes with cross-browser development, time must be spent to work out the kinks in different browsers. Firebug is by far the superior tool, but if you're troubleshooting a bug in IE, it goes without saying that the IE Dev tool would be the better choice.
Also, since we are still coding for multiple versions of IE. IE 7 compatibility mode is a nice feature to test that you're latest changes that seem to work fine in IE8 are still working/looking like you would expect them to in IE7.
I think you will have to learn both, because sometimes things that work in FF don't work as expected in IE, or the other way round, so it will be helpful to use the tool that matches the browser.
Инструменты разработки в Firefox и IE теперь одинаковы после появления IE8. Да, это означает, что Internet Explorer по-прежнему не является выбором разработчиков по многим причинам, однако основным инструментом FF, известным в разработчиках, является Firebug, а другим - панель инструментов веб-разработчика, ну, инструменты разработчика IE охватывают оба из них, и если вы знакомы с IE Developer Tools или Firebug на FF, у вас не должно быть никаких проблем с работой в другом браузере.
Этот учебник полезен: Учебник: Использование инструментов разработчика IE в качестве Firebug в Mozilla Firefox