Firefox is still king for developers

Firefox is still king for developers

Summary: Firefox is still king when it comes to daily work on the tubes, despite the steady increase in the buzz surrounding the open-source Webkit project, on which Safari and Google Chrome are based.


Firefox is still king when it comes to daily work on the tubes, despite the steady increase in the buzz surrounding the open-source Webkit project, on which Safari and Google Chrome are based.

With each passing day the Webkit hype-machine grows: Webkit-based Safari 4 is a fast, standards-compliant browser that is at the top of the pack in terms of page rendering; since November there have been wishful rumours of IE switching its rendering engine to Webkit; and it also is the engine behind Google Chrome and Adobe AIR.

I myself use Webkit nightlies as my primary browser of choice on my MacBook, however, when the need for HTML development or inspection occurs, it's time to start up Firefox. I have a few clear cut reasons for this.

1. View selection source
Although Safari 4 officially introduced the browser's new development tools, the simple matter is that Firefox's is better. Take for instance the common example of wanting to view the source code of a particular area of a page.

Safari hides the selected text inside the highlighted <p> tag.
(Credit: Chris Duckett/

  (Credit: Chris Duckett/

When choosing "Inspect Element" within Webkit, the text that we are after is within the highlighted <p> tag. Within Firefox, the selection I am after is shown immediately to me and highlighted.

I'll be the first to admit that this is a trivial example, it is trivial to open the highlighted <p> tag, and that Webkit's tools give a better idea of the surrounding HTML than the Firefox example.

But programming efficiency is all about removing these trivialisations — if I need to open a rolled up tag 50 times a day then that is 50 more times I'll be annoyed. And developers are angry enough as it is.

2. Plug-ins
While Webkit's development tools are nice, they are much the same as the Firebug set of tools that have been around for a lot longer and are available as a plug-in for Firefox. When the next leap in browser-based development tools occurs, I'll bet that it will happen on Firefox. Plug-ins are a lot easier to create and are more flexible than attempting to get an untested tool committed to into a project's trunk.

3. Squirrelfish is flaky
Despite what the marketing honchos at Apple may want you to call it, that new "Nitro" engine is actually an unholy alliance between a friendly squirrel and an emotionally stable fish who loved each other very much.

And although Squirrelfish (Webkit's Java interpreter) is blisteringly fast, it still has aspects of it that are "flaky". I assume that this is because it is a lot stricter on what it will execute than Firefox or IE. A particular banking site I know of has to be used in Firefox if you want to have particular fields auto-completed. It's another one of those small bugs that hold Webkit back.

Closing thoughts
The old adage of "the right tool for the job" is true in life and therefore true for web development.

Webkit is a great everyday browser that has minor quirks that will occasionally need you to find another browser for an older site. But Firefox is the tool of choice to getting down and dirty in code. Firefox plays to its strength that it was developed by geeks, for geeks — and has an unbeatable repertoire of development tools to choose from.

As for using Internet Explorer, excuse me while I find something less painful to pursue.

Topics: Software Development, Browser, IT Employment


Chris started his journalistic adventure in 2006 as the Editor of Builder AU after originally joining CBS as a programmer. After a Canadian sojourn, he returned in 2011 as the Editor of TechRepublic Australia, and is now the Australian Editor of ZDNet.

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


Log in or register to join the discussion
  • Blahhhhhhh

    I'm an old-school web developer so please excuse me whilst I choke. Notepad is still the king for code. I don't have any trouble rolling out web pages. Yes I do use Firefox and Safari as well as IE with the former two both on Windows and Apple machines but this is merely to test that anything I set up works across all browsers.

    You younger blokes always make web development sound like it needs specialist tools and an underlying allegience to open source products to work efficiently but in reality this article is more of a silly attack on Microsoft which good journalism should be well above.

    The comment about geeks in the second last paragraph is a laugh too and very stereotypical. Next you'll be saying that you survive only on Coke and pizza with double anchovies and that your five o'clock shadow is there to impress your haxor mates.
  • Debugging, not writing of code

    Hey Mel,

    I was only referring to browsers used as debugging tools during development. I also use a basic text editor (by choice) when writing code -- can't say I'm a fan of IDEs at all.
  • Sounds good

    Okay, fair enough. Thankyou for the clarification. :-)
  • Live changes

    Its also hard to code using PHP with just a plain text editor because its a live environment. Using firebug on a functioning page means you can make changes and instantly see the impact, then make the required change to the code via text editor.

    Without handy tools like this the time invested in 'polishing' after the basic development is complete would be significantly longer.

    As far as IE goes, its troubled implementation of standards and changing standards from IE 5 to 6, 6 to 7, and now 7 to 8, its no surprise that it frustrates web developers no end. At least (from my meager testing) IE8 finally seems standards compliant, at least to the same level as Firefox and Safari.
  • Anchovies contribute to poor coding style.

    16-inch rotary debugger: A highly effective tool for locating problems in computer software. Available for delivery in most major metropolitan areas. Anchovies contribute to poor coding style.

    -- Amiga ROM Kernel Manual (Glossary)
  • its not FF but Firebug that is king

    Firefox stays where it is due to 2 plugins - Firebug and Web Developer. Without these, I doubt very much if developers would care either way. The downside of FF's amazing ability to handle bad html is that while everything works in FF when the developer uses it, and tester's crib when they look at the same page in IE. What I'd love is for Firebug to work as well in IE - I would switch, because while developers prefer FF, my users prefer IE.