26.04.2015 Views

Founders at Work.pdf

Founders at Work.pdf

Founders at Work.pdf

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Blake Ross 397<br />

open source d<strong>at</strong>abase already called Firebird. So we renamed it again. At th<strong>at</strong><br />

point, it was fairly popular—though not nearly as popular as it is now—so we<br />

wanted to keep the “Fire” part of the name. We just went through Fireanything<br />

names for a couple of months, and somebody came up with Firefox,<br />

which is actually the Chinese name for a red panda.<br />

Livingston: Were the Firefox developers all in different places?<br />

Ross: When we first started doing it, we were all <strong>at</strong> Netscape. Then Dave left to<br />

go to Apple to work on Safari, and we had some other folks like Ben Goodger<br />

from New Zealand, Pierre Chanial from France, and Jan Varga from Slovakia<br />

come on board. I went back to Miami, and we continued to work together<br />

online.<br />

Joe and I still collabor<strong>at</strong>e through IM on Parakey, even though we’re about<br />

20 minutes apart, because we’re so used to th<strong>at</strong> environment from Firefox. It’s<br />

just so much faster to collabor<strong>at</strong>e online than it is for him to drive down to me<br />

or me to drive up to him.<br />

Livingston: Were there any conflicts with Dave working <strong>at</strong> Apple?<br />

Ross: Yes. They were also making a simple end-user browser, and he was not<br />

really supposed to be working on a competitor to th<strong>at</strong>. It wasn’t on our end th<strong>at</strong><br />

we had a problem.<br />

Livingston: Did he leave Apple?<br />

Ross: No. He still works on Safari right now. He did Firefox and then went off<br />

to Apple.<br />

Livingston: So then it was just a few of you.<br />

Ross: The Firefox team is always changing. It’s not fair to say there are just a<br />

few of us, because we’re based on Mozilla, which obviously has dozens of developers,<br />

and there are a lot of developers working on Gecko, the core layout<br />

engine. The Firefox team itself—the people worrying about everything wrapped<br />

around the engine and working on the separ<strong>at</strong>e fork of the code base—was<br />

always about four or five different people for the first year.<br />

Now there are a lot more, obviously, because it’s the main source tree. All<br />

those people th<strong>at</strong> were working on Mozilla now work on Firefox.<br />

Livingston: Wh<strong>at</strong> was the first turning point when you knew you were really<br />

onto something?<br />

Ross: I think it was when we put out our first milestone, which wasn’t even . . .<br />

We put it on an FTP site and had an article on mozillaZine, which is a community<br />

news site. It was already getting as many downloads as a Mozilla milestone.<br />

On the one side, you had a lot of Mozilla people—the hardcore developer<br />

types—who didn’t like wh<strong>at</strong> we were doing, because focusing on “mom and<br />

dad” is heretical in much of the open source world. Then there were a lot of<br />

people who were saying, “Finally, Mozilla is stepping away from its geek roots<br />

and doing something more mainstream.” We got a lot of coverage early on from<br />

bloggers and PC World and stuff like th<strong>at</strong>. It got out of control pretty quickly.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!