The Story of Firefox: from Underdog to Superhero
It took some time for Mozilla to come of age post-Netscape. Although Netscape Communicator's source code was released in early 1998, the Mozilla 1.0 suite, or applications framework as it is technically called, was not finished until June 5, 2002. Despite Mozilla's Netscape-like look and feel during this period, much was changing under the hood. In November 2000, Linux Journal writer Mike Angelo commented that “if you have any notions that Mozilla, the browser suite, is an upgrade from Netscape Communicator 4.x, please lose them. Picture Mozilla as a browser suite that is new from the ground up, but just looks and feels lots like the Netscape 4.x browser suite, thanks to its skin”.
In spite of the overhaul, Mozilla retained Netscape's “all-in-one” suite orientation, which was later to be shed by the self-standing Firefox. Mozilla consisted of the applications Mozilla Navigator, Mozilla Composer, Mozilla E-Mail, Mozilla News and ChatZilla.
During this period, in March 1999, Netscape went off to become part of America Online. Nevertheless, the two organizations retained close ties—for instance, many of Mozilla's developers were inside Netscape/AOL, and Netscape/AOL continued to assist Mozilla financially. Furthermore, while Netscape/AOL utilized the Mozilla code as a base for its own Netscape 6, the company added its own proprietary features, such as AIM.
Development-wise, these six interim years were productive. Most important, the Mozilla development team built the Gecko browser layout engine from scratch and ensured full W3C (World Wide Web Consortium) standards compliance. In addition, changing skins on the fly, security features and the plugin model were expanded and improved significantly.
After four long years of development, Mozilla 1.0, mostly free of its Netscape Communicator past, was at last released on June 4, 2002. CNET.com's Rex Baldazo raved that “The four-and-a-half-year wait is over—Mozilla 1.0 has gone gold, and from what we've seen, it's been worth the delay.” Immediately, users were impressed with Mozilla's speed, stability and features, such as tabbed browsing, pop-up blocking and custom skins.
Mozilla's features caught the surfing public's attention and re-ignited the browser wars of yore. Several different Web analytics firms reported that Microsoft's Internet Explorer dropped from a 97% market share in 2002 to 93% in late 2004. During the same period, Mozilla went from a 2% market share with Netscape to more than 5% with all of its open-source browser offerings.
While the Mozilla browser was out in the world making Web surfers everywhere gleeful, the development team at mozilla.org, led by Chief Technology Officer Brendan Eich, already was laying the foundation for a much better browser. On September 23, 2002, the Mozilla team released Phoenix 0.1 (Pescadero), the first official version of a standalone browser that would later be named Firebird and, eventually, Firefox. Phoenix was a redesign of Mozilla's browser component but written using the XUL user interface language and designed to be cross-platform. Phoenix's developers stated that “Phoenix is not your father's Mozilla browser. It's a lean and fast browser that doesn't skimp on features”, loading pages in half the time as Mozilla 1.1. Furthermore, they added, “Not only does Phoenix aim to match the feature set of Mozilla—subtracting features deemed geeky and better offered as add-ons—but it extends it. We also believe Mozilla, in general, is going in the wrong direction in terms of bloat and UI, and see no reason for our releases to carry those connotations.”
On April 3, 2003, Mozilla announced its intent to develop what would become Firefox (code-named Firebird at the time) as a standalone application rather than as part of an integrated suite.
Mozilla's Eich summarized the new browser's philosophy in its development road map as follows:
[Firefox] is simply smaller, faster, and better—especially better not because it has every conflicting feature wanted by each segment of the Mozilla community, but because it has a strong “add-on” extension mechanism....Attempting to “hard-wire” all these features to the integrated application suite is not legitimate; it's neither technically nor socially scalable.
Six years, seven months and nine days after the birth of mozilla.org, Firefox 1.0 was born on November 9, 2004. Looking back to the earliest days of Firefox 1.0 with three and a half years of perspective and comfortable browsing, it's easy to forget how exciting the post-release vibe was. Firefox saw more than 100,000 downloads in the first few hours and nearly 10 million per month shortly after the release. Toward the end of its run, Firefox 1.0 reached 100 million downloads in October 2005. This success translated into a market share of around 5%. By early December 2004, according to OnStat.com, Internet Explorer's market share dropped yet again to below 90%.
There was a palpable hunger for an alternative. As part of the Spread Firefox campaign, 10,000 Firefox supporters coughed up some of their hard-earned money to show support for their browser by contributing to fund a full-spread advertisement in the New York Times. Spread Firefox is the nexus of global community volunteerism to promote Firefox via guerrilla marketing activities.
The left page of the masterful New York Times ad features the names of all 10,000 contributors over a shadowed Firefox logo. The ad asks the reader, “Are you fed up with your Web browser? You're not alone. We want you to know there is an alternative.” On the right page, it featured, “Introducing Mozilla Firefox 1.0” in bold type, followed by quotes from satisfied users and the advantages of Firefox, such as speed and browsing free of pop-ups and spyware. “Find out what 10 million users from around the world already know: there is an alternative.” Unfortunately, the Times ad is not printable in this space due to size constraints, although you can see it at the Spread Firefox Web site.
There also was hunger for better security. On the Windows side, it seemed that IE was once invincible. However, IE's security problems pushed millions of users and countless organizations out to the far edge of the plank; Firefox was the nudge that made them jump ship in droves.
For most people, however, the reason to move to Firefox was its features. They ate up the tabbed browsing, better standards support, integrated search, a user-friendly plugin management system, easy installation and removal procedures and, of course, better security. The latter was possible, because Firefox lacks the deep hooks into the operating system as is the situation with IE, which therefore suffers greater impact from flaws.
James Gray is Products Editor for Linux Journal.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Tech Tip: Really Simple HTTP Server with Python
- Doing for User Space What We Did for Kernel Space
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
- SuperTuxKart 0.9.2 Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide