5 ms·

With no doubt, the Firebug team can take credit for changing the world of Web development. These guys aren't giving themselves enough credit. IMO, they can ta

by dboyd 16y ago

With no doubt, the Firebug team can take credit for changing the world of Web development. These guys aren't giving themselves enough credit. IMO, they can take credit for advancing the world of Web development. While the other development tools are (quickly) catching up, firebug is still leading the pack.

erikpukinskis 16y ago
I've pretty happily switched to Chrome, which seems to do everything I used to ask Firebug to do. Although honestly I no longer use Firebug because I no longer use Firefox, and I no longer use Firefox because it takes up an obscene amount of vertical real estate compared to Chrome.
- BrandonM 16y ago
  My Firefox takes up less vertical real estate than Chrome. I use Tiny Menu, customize the toolbars to put everything into the menu bar, and use Tree-Style Tabs to show the tabs vertically along the right side. The best option I have at work is Chrome, and having the tabs along the top is much less usable compared to Tree-Style Tabs.
  - sjs 16y ago
    It's subjective. I tried and hated tree style tabs. I prefer Chrome these days but Firefox and Safari are still up there, and also fast[1]. It's just nice to have a variety of good browsers to choose from. [1] http://arewefastyet.com http://arewefastyet.com (doesn't say "no" anymore)
    - BrandonM 16y ago
      I didn't say Tree Style tabs were better, only more usable (for me). I can have 30 tabs open and see a pretty wide portion of the page title. I sacrifice horizontal real estate (which is often wasted) for vertical real estate. I can understand not liking tree style tabs for various reasons, but saying that their improved usability is subjective is a bit of a stretch.
      - sjs 16y ago
        If someone only ever has 3 tabs open then tree-style is a waste of space. How is it not subjective? It depends entirely on the user's browsing habits.
- catch23 16y ago
  there are some things the chrome/webkit debugger still lacks compared to firebug though. I like how firebug always shows a stack trace when there are errors during runtime. In chrome/webkit, you just get a little red x in the console with an error message, but you have to find out the root cause yourself.
- masklinn 16y ago
  > and I no longer use Firefox because it takes up an obscene amount of vertical real estate compared to Chrome. Obscene? On OSX with Firefox 3.6 and Chrome 6, the difference is about the height of Firefox's tabs on top, with the web developer toolbar enabled. Disable/hide the web dev toolbar and the difference is a few pixels in favor of Chrome. nb: status bar and bookmarks toolbar disabled in Firefox.
  - guelo 16y ago
    I just measured a 50px difference in my configuration, that is including Firefox's Status bar at the bottom and not including Chrome's 20px fly-out link hover thing at the bottom left. Of course you can completely change Firefox around if you you want.
- rottencupcakes 16y ago
  Personally I browse in Chrome, but the second I start debugging JS/AJAX i'll open Firefox and use that. It's 10x slower, it has Memory leaks up the wazoo, but firebug blows chrome's debugger out of the water.
  - masklinn 16y ago
    > but firebug blows chrome's debugger out of the water. Could you please describes the ways in which it "blows chrome's debugger" [actually the Webkit Development Tools, it's been much more than a debugger for quite a long time) "out of the water" in your opinion?
    - nowarninglabel 16y ago
      Yeah, I'd also like to see an analysis of this. I used to be an automatic 'switch to Firefox for debugging' user, but I find that the Chrome developer tools are now pretty sufficient.
      - etherealG 16y ago
        a small example, not really analysis, but it does count. one of the reasons I still use ff instead of chrome for debugging is that on post requests viewing the raw source of a page requires chrome to repost to the server. ff just shows me the page/data as it came back without the repost, which can be critical in debugging stateful posts where a double post effects state.
        masklinn 16y ago
        I'll have to test that, that doesn't seem to happen in the resource viewer of Safari 5.
    - jlangenauer 16y ago
      Here's one example: I've found that in certain cases Chrome's debugger sometimes can't link back to the line number where an error is caused when that line is inside an anonymous function, whereas Firebug often can. That said, I do most of my debugging in Chrome, only switching to Firefox/Firebug when they fail me, which isn't too often.
- Timmy_C 16y ago
  I do a lot of Omniture and DoubleClick analytics development and I find that Firebug plugins like Omnibug are irreplaceable. Is there an equivalent debugging tool for Chrome?
  - masklinn 16y ago
    Not that I know of: the webkit dev tools aren't externally pluggable (if they are I missed how, but since Chrome and Safari have different plugin architectures I don't see how that would work), so third-parties (to both the browser and the tools, but for Webkit browsers they're kind-of merged) can not extend the tools aside from getting patches merged into mainline.
- carbon8 16y ago
  The webkit nightlies tend to have more features. There is still one behavior that frustrates me every time I use the webkit tools, though: clicking on an asset link (eg, to a javascript file) brings up the resource tracker rather than the file.
  - armandososa 16y ago
    There are a lot of tiny little details like that, that in sum make webkit's inspector not as a good experience as firebug
- erikano 16y ago
  > [...] I no longer use Firefox because it takes up an obscene amount of vertical real estate compared to Chrome. Have you tried the add-ons Vimperator + "Tree Style Tab" (remember to activate "Auto hide tab bar")?
- csytan 16y ago
  This is true, but ironically Chrome's dev tools take up more vertical space than Firebug. I'm happy I've made the switch, though it would be nice if Chrome/webkit traded some flashy icons for a more space efficient table especially in the "Resources" tab.
  - masklinn 16y ago
    If your issue is with the size of the resource icons in the left-hand pane, the inspector (Safari's anyway) has an option called "Use Large resource Rows" which is enabled by default (4th from the left). If you disable it, the lines will be as big as the resource's name itself, without the big icons and the domain.
- lepht 16y ago
  Chrome is also my primary browser, but I wanted to point out a discovery I made today: The Chromifox Extreme[1] Firefox theme in combination with its bundled helper extension completely negates the vertical pixel space waste in Firefox vs. Chrome, at least in Mac OS. I'm actually using the carbon variant[2] in combination with the Omnibar extension[3] to combine the URL and search bars. [1] https://addons.mozilla.org/en-US/firefox/addon/10674/ https://addons.mozilla.org/en-US/firefox/addon/10674/ [2] https://addons.mozilla.org/en-US/firefox/addon/10883/ https://addons.mozilla.org/en-US/firefox/addon/10883/ [3] https://addons.mozilla.org/en-US/firefox/addon/8823/ https://addons.mozilla.org/en-US/firefox/addon/8823/
  - josh33 16y ago
    I just installed all three. Real-estate problem solved for me
- brendoncrawford 16y ago
  Grab the "Chromifox Extreme" and "Hide Menubar" extensions for FF 3.6. These will give almost the exact same vertical screen space.
- SkyMarshal 16y ago
  'Obscene' is an overstatement. FF vs Chrome: http://imgur.com/P5Mw6.png http://imgur.com/P5Mw6.png
deleted 16y ago
[deleted]

by dboyd 16y ago

erikpukinskis 16y ago

I've pretty happily switched to Chrome, which seems to do everything I used to ask Firebug to do. Although honestly I no longer use Firebug because I no longer use Firefox, and I no longer use Firefox because it takes up an obscene amount of vertical real estate compared to Chrome.

BrandonM 16y ago
My Firefox takes up less vertical real estate than Chrome. I use Tiny Menu, customize the toolbars to put everything into the menu bar, and use Tree-Style Tabs to show the tabs vertically along the right side. The best option I have at work is Chrome, and having the tabs along the top is much less usable compared to Tree-Style Tabs.
- sjs 16y ago
  It's subjective. I tried and hated tree style tabs. I prefer Chrome these days but Firefox and Safari are still up there, and also fast[1]. It's just nice to have a variety of good browsers to choose from. [1] http://arewefastyet.com http://arewefastyet.com (doesn't say "no" anymore)
  - BrandonM 16y ago
    I didn't say Tree Style tabs were better, only more usable (for me). I can have 30 tabs open and see a pretty wide portion of the page title. I sacrifice horizontal real estate (which is often wasted) for vertical real estate. I can understand not liking tree style tabs for various reasons, but saying that their improved usability is subjective is a bit of a stretch.
    - sjs 16y ago
      If someone only ever has 3 tabs open then tree-style is a waste of space. How is it not subjective? It depends entirely on the user's browsing habits.
catch23 16y ago
there are some things the chrome/webkit debugger still lacks compared to firebug though. I like how firebug always shows a stack trace when there are errors during runtime. In chrome/webkit, you just get a little red x in the console with an error message, but you have to find out the root cause yourself.
masklinn 16y ago
> and I no longer use Firefox because it takes up an obscene amount of vertical real estate compared to Chrome. Obscene? On OSX with Firefox 3.6 and Chrome 6, the difference is about the height of Firefox's tabs on top, with the web developer toolbar enabled. Disable/hide the web dev toolbar and the difference is a few pixels in favor of Chrome. nb: status bar and bookmarks toolbar disabled in Firefox.
- guelo 16y ago
  I just measured a 50px difference in my configuration, that is including Firefox's Status bar at the bottom and not including Chrome's 20px fly-out link hover thing at the bottom left. Of course you can completely change Firefox around if you you want.
rottencupcakes 16y ago
Personally I browse in Chrome, but the second I start debugging JS/AJAX i'll open Firefox and use that. It's 10x slower, it has Memory leaks up the wazoo, but firebug blows chrome's debugger out of the water.
- masklinn 16y ago
  > but firebug blows chrome's debugger out of the water. Could you please describes the ways in which it "blows chrome's debugger" [actually the Webkit Development Tools, it's been much more than a debugger for quite a long time) "out of the water" in your opinion?
  - nowarninglabel 16y ago
    Yeah, I'd also like to see an analysis of this. I used to be an automatic 'switch to Firefox for debugging' user, but I find that the Chrome developer tools are now pretty sufficient.
    - etherealG 16y ago
      a small example, not really analysis, but it does count. one of the reasons I still use ff instead of chrome for debugging is that on post requests viewing the raw source of a page requires chrome to repost to the server. ff just shows me the page/data as it came back without the repost, which can be critical in debugging stateful posts where a double post effects state.
      - masklinn 16y ago
        I'll have to test that, that doesn't seem to happen in the resource viewer of Safari 5.
  - jlangenauer 16y ago
    Here's one example: I've found that in certain cases Chrome's debugger sometimes can't link back to the line number where an error is caused when that line is inside an anonymous function, whereas Firebug often can. That said, I do most of my debugging in Chrome, only switching to Firefox/Firebug when they fail me, which isn't too often.
Timmy_C 16y ago
I do a lot of Omniture and DoubleClick analytics development and I find that Firebug plugins like Omnibug are irreplaceable. Is there an equivalent debugging tool for Chrome?
- masklinn 16y ago
  Not that I know of: the webkit dev tools aren't externally pluggable (if they are I missed how, but since Chrome and Safari have different plugin architectures I don't see how that would work), so third-parties (to both the browser and the tools, but for Webkit browsers they're kind-of merged) can not extend the tools aside from getting patches merged into mainline.
carbon8 16y ago
The webkit nightlies tend to have more features. There is still one behavior that frustrates me every time I use the webkit tools, though: clicking on an asset link (eg, to a javascript file) brings up the resource tracker rather than the file.
- armandososa 16y ago
  There are a lot of tiny little details like that, that in sum make webkit's inspector not as a good experience as firebug
erikano 16y ago
> [...] I no longer use Firefox because it takes up an obscene amount of vertical real estate compared to Chrome. Have you tried the add-ons Vimperator + "Tree Style Tab" (remember to activate "Auto hide tab bar")?
csytan 16y ago
This is true, but ironically Chrome's dev tools take up more vertical space than Firebug. I'm happy I've made the switch, though it would be nice if Chrome/webkit traded some flashy icons for a more space efficient table especially in the "Resources" tab.
- masklinn 16y ago
  If your issue is with the size of the resource icons in the left-hand pane, the inspector (Safari's anyway) has an option called "Use Large resource Rows" which is enabled by default (4th from the left). If you disable it, the lines will be as big as the resource's name itself, without the big icons and the domain.
lepht 16y ago
Chrome is also my primary browser, but I wanted to point out a discovery I made today: The Chromifox Extreme[1] Firefox theme in combination with its bundled helper extension completely negates the vertical pixel space waste in Firefox vs. Chrome, at least in Mac OS. I'm actually using the carbon variant[2] in combination with the Omnibar extension[3] to combine the URL and search bars. [1] https://addons.mozilla.org/en-US/firefox/addon/10674/ https://addons.mozilla.org/en-US/firefox/addon/10674/ [2] https://addons.mozilla.org/en-US/firefox/addon/10883/ https://addons.mozilla.org/en-US/firefox/addon/10883/ [3] https://addons.mozilla.org/en-US/firefox/addon/8823/ https://addons.mozilla.org/en-US/firefox/addon/8823/
- josh33 16y ago
  I just installed all three. Real-estate problem solved for me
brendoncrawford 16y ago
Grab the "Chromifox Extreme" and "Hide Menubar" extensions for FF 3.6. These will give almost the exact same vertical screen space.
SkyMarshal 16y ago
'Obscene' is an overstatement. FF vs Chrome: http://imgur.com/P5Mw6.png http://imgur.com/P5Mw6.png

deleted 16y ago

[deleted]