MozillaZine

Our First Weekend Discussion

Friday February 11th, 2000

I've decided to try something new at MozillaZine: a "weekend discussion". Every Friday, we'll have a forum on a topic of interest to Mozilla users and developers. Hopefully it will generate some interesting conversations.

This week's topic is "Web Standards". What are your feelings about the current standards "process"? About Mozilla and its standards support? About what standards Mozilla should support in the future? I'm also interested in getting some opinions from Mozilla developers on this issue. How do they feel about being the "guinea pigs" of the standards process, being the first to implement standards specifications and also being the ones to deal with the vagaries and inconsistencies between revisions in the current specs? How are developers feeling about Mozilla's standards support so far?

Our forums are quite civil, so don't be afraid to speak your mind. We'd love to hear what you have to say. Just click the "responses" link below to get started.


#12 Why exactly is that?

by mozineAdmin

Friday February 11th, 2000 4:20 PM

You are replying to this message

Just because Netscape uses the Mozilla code for Netscape 5 does not make Mozilla less worthy of becoming the reference implementation. It is, in fact, the only browser that could *possibly* become a reference implementation at this point, because of its well-supported open development process.

Netscape unleashed the source code. But the source code that we have today shares very little in common with Communicator 4.x. Mozilla has grown in an open environment, and it is ideally suited to the task of becoming the reference implementation.

The only other option would be to take the Mozilla code and create an entirely new development tree, which would be a huge waste of effort. Or, they could see if they could get public support for the Amaya browser. I don't see that happening. It certainly hasn't so far.

No one is forced to comply with the standards (see today's current situation for proof of that). It could not possibly become "Microsoft II", because the public would be allowed to comment on and correct the Mozilla implementation. If there were problems with Mozilla's code, those problems would have to be fixed (just as they would in any other browser).

It might give Mozilla a home court advantage, so to speak, but they already have that, IMO. They're the only group out there putting their code on the line. If MS opened up their development process, then we would have two possibilities for "reference implementation". I don't see that happening, either.