Diff for /books/www/articles/bloom.html between versions 1.15 and 1.16

version 1.15, 2002/09/03 03:58:19 version 1.16, 2002/09/03 17:39:42
Line 1 Line 1
 <h1>Let a Hundred Browsers Bloom</h1>  <h1>Let a Hundred Browsers Bloom</h1>
   
   
<p>The recently released <a href="http://wp.netscape.com/eng/mozilla/ns7/relnotes/7.html">Netscape 7</a> may be the most well known browser built with Mozilla, but it certainly is not the only one.  Mozilla is being used as a framework to create many different types of applications including OEone's <a href="http://oeone.com/products/desktop.html">HomeBase DESKTOP</a>, ActiveState's <a href="http://activestate.com/Products/Komodo/">Komodo IDE</a>, and <a href="http://www.mozdev.org/projects.html">all of the projects</a> hosted on mozdev.org.  People are also using Mozilla to create their own custom browsers [link to brian's article].<p>The recently released <a href="http://wp.netscape.com/eng/mozilla/ns7/relnotes/7.html">Netscape 7</a> may be the most well known
 browser built with Mozilla, but it certainly is not the only one.  Mozilla is being used as a framework to create many different types of
 applications including OEone's <a href="http://oeone.com/products/desktop.html">HomeBase DESKTOP</a>, ActiveState's <a
 href="http://activestate.com/Products/Komodo/">Komodo IDE</a>, and <a href="http://www.mozdev.org/projects.html">all of the projects</a>
 hosted on mozdev.org.  People are also using Mozilla to create their own custom browsers <i>[link to brian's article]</i>.  This article
 provides a survey of most currently available Mozilla browsers, so you can try them out and find the one that works best for you.
   
   
 <h2>Why Do We Need More Than One?</h2>  <h2>Why Do We Need More Than One?</h2>
   
<p>One of the benefits of Open Source development is that it prevents someone from having to reinvent the wheel whenever they are working on developing something that has been done before.  Since the Mozilla community is already working on a browser, wouldn't it be better if everyone just focused on making that browser as good as it can be?<p>One of the benefits of Open Source development is that it prevents someone from having to reinvent the wheel whenever they are working
on developing something that has been done before.  Since the Mozilla community is already working on a browser, wouldn't it be better if
<p>Instead of being a bad thing, the several different browser development projects that are currently underway are one of the Mozilla community's greatest assets for the simple reason that one browser can not be all things to all people.  Each new browser that gets built is filling a need that is not being met by any other existing option.  Each new browser that is built also has the potential to appeal to a whole new audience that will help expand Mozilla's adoption.everyone just focused on making that browser as good as it can be?
<p>Another positive benefit of having multiple browsers is that it helps avoid compromises that don't make anyone happy.  AOL is interesting in Mozilla because they want a browser that appeals to novice Internet users.  The Mozilla developers who contribute their time to the project want to create a powerful browser with a collection of advanced features.  If the community is locked into working on only one browser, then the end result of this development process will be a browser that has a bewildering array of features and that doesn't appeal to either intended audience.<p>Instead of being a bad thing, the several different browser development projects that are currently underway are one of the Mozilla
community's greatest assets.  The simple reason for this is that one browser can not be all things to all people.  Each new type of
<p>If one browser can't possibly to beginning users and power users at the same time, why not create two different browsers?  For that matter, why not create as many different browsers as there are different types of users?  Since all of these browsers are built using Mozilla, web developers can create sites that work with Mozilla and users can browse with whatever tool suits them best.  Everyone wins.browser that gets built is filling a need that is not being met by any other existing option.  Each new browser that is built also has
 the potential to appeal to a whole new audience that will help expand Mozilla's adoption.
 
 <p>Another positive benefit of having multiple browsers is that it helps avoid compromises that don't make anyone happy.  AOL is
 interested in using Mozilla to create a browser that appeals to novice Internet users.  The Mozilla developers who contribute their time
 to the project want to create a powerful browser with a collection of advanced features.  If the community is locked into working on only
 one browser, then the end result of this development process will be a browser that has a bewildering array of features and that doesn't
 appeal to either intended audience.
 
 <p>If one browser can't possibly appeal to beginning users and power users at the same time, why not create two different browsers?  For
 that matter, why not create as many different browsers as there are different types of users?  Since all of these browsers are built
 using Mozilla, web developers can create sites using standards such as HTML, CSS and DOM that work well with all of these browsers and
 users can browse the web with whatever tool suits them best.  Everyone wins.
   
   
 <h2>Gecko Based Browsers</h2>  <h2>Gecko Based Browsers</h2>
   
<p>There are two main types of browsers that are built using Mozilla.  Some developers choose to create their application using XUL, Mozilla's XML-based User Interface language.  Other developers prefer to use just Gecko, Mozilla's rendering, and then create the GUI of their browser using one of the toolkits native to a specific platform.  There are Gecko based browsers for each of the major operating systems in use today, including Windows, Linux and Mac OS X.<p>There are two main types of browsers that are built using Mozilla.  Some developers choose to create their application using XUL,
Mozilla's cross-platform XML-based User Interface language.  Other developers prefer to use just Gecko, Mozilla's rendering engine, and
<p>The goal of the <a href="http://chimera.mozdev.org">Chimera</a> project is to create a best-of-breed browser for the Mac OS X platform with an user-interface that is as simple and as clean as possible.  Chimera uses <a href="http://www.mozilla.org/ports/fizzilla/Cocoazilla.html">Cocoazilla</a>, a variant of <a href="http://www.mozilla.org/ports/fizzilla/">Fizzilla</a> that consists of a UNIX back end connected to a Cocoa front end.  Since Chimera uses a native toolkit to create it's GUI it can't run on any platform other than OS X, but since it doesn't use XUL it is faster than the default Mozilla browser on the same computer (applications written with XUL will always be slightly slower than applications written with native toolkits because *** need explanation here, ask brian ***).  The most recent stable release, <a href="ftp://ftp.mozilla.org/pub/chimera/releases/chimera-0.4.dmg.gz">version 0.4</a>, is available for download along with <a href="ftp://ftp.mozilla.org/pub/chimera/nightly/latest-trunk/">nightly development builds</a>.then create the interface of their browser using one of the toolkits native to a specific platform.  There are Gecko based browsers for
each of the major operating systems in use today, including Windows, Linux and Mac OS X.
<p><img src="http://idisk.mac.com/mozilladave/Public/chimera.jpg"><br>
<font size="-1">Chimera with sidebar open</font><p>The goal of the <a href="http://chimera.mozdev.org">Chimera</a> project is to create a best-of-breed browser for the Mac OS X platform
with a user-interface that is as simple and as clean as possible.  Chimera uses <a
<p><a href="http://galeon.sourceforge.net">Galeon</a> and <a href="http://kmeleon.sourceforge.net">K-Meleon</a> are projects that also have the goal of creating a simple standards-compliant browser using Mozilla's rendering engine.  Galeon uses Gecko to create a browser for the <a href="http://www.gnome.org/">GNOME</a> desktop and K-Meleon uses Gecko to create a Windows only browser.  The latest stable version of Galeon can be <a href="http://galeon.sourceforge.net/download/">downloaded</a> for a variety of Linux distributions.  There are also alpha versions available for <a href="http://galeon.sourceforge.net/galeon2/">Galeon2</a>, which is a new major version of the browser that takes advantage of the huge changes in architecture in the new GNOME 2 desktop.  The latest version of K-Meleon can be <a href="http://kmeleon.sourceforge.net/download.php">downloaded</a> for Windows and it includes a number of stability and configuration changes over earlier versions.  Other Gecko based browsers include <a href="http://www.muhri.net/skipstone">SkipStone</a> and <a href="http://qbati2.sourceforge.net">Q.Bati</a>.href="http://www.mozilla.org/ports/fizzilla/Cocoazilla.html">Cocoazilla</a>, a variant of <a
 href="http://www.mozilla.org/ports/fizzilla/">Fizzilla</a> that consists of a UNIX back end connected to a Cocoa front end.  Since
 Chimera uses a native toolkit to create it's GUI it can't run on any platform other than OS X, but since it doesn't use XUL it is faster
 than the default Mozilla browser on the same computer (applications written with XUL will always be slightly slower than applications
 written with native toolkits because *** need explanation here, ask brian ***).  The most recent stable release, <a
 href="ftp://ftp.mozilla.org/pub/chimera/releases/chimera-0.4.dmg.gz">version 0.4</a>, is available for download along with <a
 href="ftp://ftp.mozilla.org/pub/chimera/nightly/latest-trunk/">nightly development builds</a>.
 
 <p><img src="http://idisk.mac.com/mozilladave/Public/chimera.jpg"><br> <font size="-1">Chimera with sidebar open</font>
 
 <p><a href="http://galeon.sourceforge.net">Galeon</a> and <a href="http://kmeleon.sourceforge.net">K-Meleon</a> are projects that also
 have the goal of creating a simple standards-compliant browser using Mozilla's rendering engine.  Galeon uses Gecko to create a browser
 for the <a href="http://www.gnome.org/">GNOME</a> desktop and K-Meleon uses Gecko to create a Windows only browser.  The latest stable
 version of Galeon can be <a href="http://galeon.sourceforge.net/download/">downloaded</a> for a variety of Linux distributions.  There
 are also alpha versions available for <a href="http://galeon.sourceforge.net/galeon2/">Galeon2</a>, which is a new major version of the
 browser that takes advantage of the huge changes in architecture in the new GNOME 2 desktop.  The latest version of K-Meleon can be <a
 href="http://kmeleon.sourceforge.net/download.php">downloaded</a> for Windows and it includes a number of stability and configuration
 changes over earlier versions.  Other Gecko based browsers include <a href="http://www.muhri.net/skipstone">SkipStone</a> and <a
 href="http://qbati2.sourceforge.net">Q.Bati</a>.
   
   
 <h2>XUL Based Browsers</h2>  <h2>XUL Based Browsers</h2>
   
<p>The other main category of Mozilla browsers include the projects building their applications using XUL.  In many ways, these projects are similar to <a href="http://mozilla.org/themes/download/">themes</a>, but they take the idea of customizing the browser one step further and use XUL, CSS, and JavaScript to change the browser interface and not just the look of the browser.  For instance, a theme developer can create new images for the buttons in the main toolbar, but a developer can edit the toolbar to add or remove buttons in their custom browser.<p>The other main category of Mozilla browsers include the projects building their applications using XUL.  In many ways, these projects
are similar to <a href="http://mozilla.org/themes/download/">themes</a>, but they take the idea of customizing the browser one step
<p>One of the first alternate browsers, <a href="http://aphrodite.mozdev.org">Aphrodite</a> was created as an alternative to the default interface that ships with Mozilla.  Aphrodite includes a number of it's own themes, including FruityGum, Inferno and two flavors of the Sullivan skin.  The crash recovery system <a href="http://aphrodite.mozdev.org/total_recall.html">Total Recall</a> is also integrated into the browser.  Development work continues on Aphrodite, although currently there isn't a new release that works with the latest version of Mozilla.further.  These custom browsers use XUL, CSS, and JavaScript to change the browser interface and not just the look of the browser.  For
instance, a theme developer can create new images for the buttons in the main toolbar, but a developer can edit the toolbar to add or
<p><img src="http://www.mozdev.org/sharedimages/sullivan_grape.gif"><br>remove buttons in their own browser.
<font size="-1">Aphrodite with the Sullivan grape theme</font>
<p>One of the first custom browsers, <a href="http://aphrodite.mozdev.org">Aphrodite</a> was created as an alternative to the default
<p><a href="http://beonex.com/communicator/">Beonex Communicator</a> is another XUL based browser that is a user-focused browsing suite that also comes bundled with a mail client and a web page editor.  The latest stable version, Communicator 0.8, is available for <a href="http://www.beonex.com/communicator/version/0.8/">download</a> for Windows and Linux.  Some other projects include <a href="http://browserg.mozdev.org">BrowserG!</a>, <a href="http://mb.mozdev.org">Project Piglet</a>, <a href="http://mercuryspider.mozdev.org/">MercurySpider</a>, and <a href="http://dino.mozdev.org">Dino</a>.interface that ships with Mozilla.  Aphrodite includes a number of it's own themes, including FruityGum, Inferno and two flavors of the
 Sullivan skin.  The crash recovery system <a href="http://aphrodite.mozdev.org/total_recall.html">Total Recall</a> is also integrated
 into the browser.  Development work continues on Aphrodite, although currently there isn't a new release that works with the latest
 version of Mozilla.
 
 <p><img src="http://www.mozdev.org/sharedimages/sullivan_grape.gif"><br> <font size="-1">Aphrodite with the Sullivan grape theme</font>
 
 <p><a href="http://beonex.com/communicator/">Beonex Communicator</a> is another XUL based browser that is a user-focused browsing suite
 that also comes bundled with a mail client and a web page editor.  The latest stable version, Communicator 0.8, is available for <a
 href="http://www.beonex.com/communicator/version/0.8/">download</a> for Windows and Linux.  Some other XUL based custom browsers include
 <a href="http://mb.mozdev.org">Project Piglet</a>, <a href="http://mercuryspider.mozdev.org/">MercurySpider</a>, and <a
 href="http://dino.mozdev.org">Dino</a>.
   
   
 <p><h2>The Future of Mozilla Browsers</h2>  <p><h2>The Future of Mozilla Browsers</h2>
   
<p>The browsers that are currently under development using Mozilla are just the tip of the iceberg.  One of the most interesting possibilities for future browser development comes from AOL, the same company that owns Netscape and that is the main sponsor of the Mozilla community.  Currently the Windows version of the AOL client uses Internet Explorer as the core of it's browser, but their are indications that this way soon change.  If AOL were to use Mozilla in a new version of their software,  tens of millions of people would be exposed to Mozilla.<p>The browsers that are currently under development using Mozilla are just the tip of the iceberg.  One of the most interesting
possibilities for future browser development comes from AOL, the same company that owns Netscape and that is the main sponsor of the
<p>AOL has already made some moves in this direction.  The latest version of the <a href="http://www.apple.com/macosx/applications/aol/">AOL client for Mac OS X</a> uses Gecko as it's rendering engine.  Gecko has also replaced Internet Explorer in <a href="http://news.com.com/2100-1023-883808.html">CompuServe 7.0</a>, the latest version of AOL's other online service.  The decision to use Gecko in these two offerings are seen by many as ways for AOL to iron out any rough spots before they move forward with releasing the latest version of their AOL client for Windows.Mozilla community.  Currently the Windows version of the AOL client software uses Internet Explorer as the core of it's browser, but
there are indications that this may soon change.  If AOL were to switch and use Mozilla in a new version of their software, tens of
<p>Another interesting project to keep on eye on is <a href="http://mozilla.org/projects/phoenix/">Phoenix</a>.  There isn't much known about this yet, but there are some pages in bugzilla and on the mozilla.org site that have some information.  It looks Phoenix is based off of an earlier project called m/b (short for mozilla/browser) and has a goal to create a user-friendly stand-alone browser that is free from most of the constraits placed on the default Mozilla browser.  Builds of Phoenix aren't available right now, but it is possible to grab the source from CVS and build it yourself right now.  There are instructions about how to do this in the project's <a href="http://lxr.mozilla.org/mozilla/source/browser/README.html">README</a> file.millions of people would be exposed to Mozilla.
<p><img src="http://www.mozillazine.org/weblogs/asa/cust3.png"><br><p>AOL has already made some moves in this direction.  The latest version of the <a
<font size="-1">Phoenix with the Customize Toolbar dialog</font>href="http://www.apple.com/macosx/applications/aol/">AOL client for Mac OS X</a> uses Gecko as it's rendering engine.  Gecko has also
replaced Internet Explorer in <a href="http://news.com.com/2100-1023-883808.html">CompuServe 7.0</a>, the latest version of AOL's other
<p>If there is a browser that you would like to use that isn't already under development, remember that you can always create your own browser with Mozilla [link to brian's article].  Each of the projects listed here could also use help with testing and development, so you can also contribute by adding features or fixing bugs to make these browsers even better.  This wealth of browser options is a great strength, so let's hope that each of these projects continue to mature and innovate.  Let 100 browsers bloom so that we can all have the perfect browser.online service.  The decision to use Gecko in these two offerings are seen by many as ways for AOL to iron out any rough spots before
 they move forward with releasing a Mozilla based version of their AOL client for Windows.
 
 <p>Another interesting project to keep on eye on is <a href="http://mozilla.org/projects/phoenix/">Phoenix</a>.  There isn't much known
 about this yet, but there are some pages in bugzilla and on the mozilla.org site that have some information.  It looks like Phoenix is
 based off of an earlier project called m/b (short for mozilla/browser) and has a goal to create a user-friendly stand-alone browser that
 is free from most of the constraits placed on the default Mozilla browser.  Builds of Phoenix aren't available right now, but it is
 possible to grab the source from Mozilla's CVS tree and build it yourself right now.  There are instructions about how to do this in the
 project's <a href="http://lxr.mozilla.org/mozilla/source/browser/README.html">README</a> file.
 
 <p><img src="http://www.mozillazine.org/weblogs/asa/cust3.png"><br> <font size="-1">Phoenix with the Customize Toolbar dialog</font>
 
 <p>If none of these browsers look like they are right for you, remember that you can always create your own browser with Mozilla <i>[link
 to brian's article]</i>.  Each of the projects listed here could also use help with testing and development, so you can also contribute
 by adding features or fixing bugs to make these browsers even better.  This wealth of browser options is a great strength, so let's hope
 that each of these projects continue to mature and innovate.  Let 100 browsers bloom so that we can all use the browser that is right 
 for us.

Removed from v.1.15  
changed lines
  Added in v.1.16


FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>