From: "Dave Ings" 

This approach could/would effectively fork the codebase. Forking codebases
in open source communities is hard to do - there is no guarantee anyone
will follow. The community can rally around the root codebase and choose to
evolve it forward. All the people in this world are very aware of this, so
I'm sure their thinking is much more along the lines of building an
ecosystem around the browser and making money around the edeges than on the
browser per se. This is a standard OSS play - you see it all the time in
this world.

I run Firefox, and I like it. It handles some things far better than IE and
so now I find I can't live without it. On the other hand it isn't feature
rich enough yet to replace IE (at least for me), so I have ended up running
both side by side, and I get to copy favourites/bookmarks back and forth
etc. This is truthfully a big pain.

So I'm not really sure that Firefox has improved my life much. :-) It has
lit a fire under Micrsoft's bum regarding browser innovation, which is a
good thing all around.
--
Regards,
Dave Ings,
Toronto, Canada

"Gary Britt"  wrote in message
news:42f3aa30{at}w3.nls.net...
> They could easily do the upgrades and new features as a proprietary add-on
> program activated in one of many ways when the generic firefox is fired
up.
> A proprietary browser helper to fire up the new proprietary dll's and
> overlays that add all the new features and functionality to the generic
> firefox, etc. etc.
>

--- BBBS/NT v4.01 Flag-5