3 ms·
> But mozilla rewrites like stylo, webrender, etc are examples of competing implementations inside the same browser. [...] This make your implyed point competin
by jcranmer 7y ago
> But mozilla rewrites like stylo, webrender, etc are examples of competing implementations inside the same browser. [...] This make your implyed point competing implementations are useful and firefox and chromium are total competing implementations vacuous.
But it doesn't. The problem with monoculture is that the bugs in the implementation tend to overrule the standard, and additionally it can make the standard impossible to implement in alternative methodology. The (P)NaCl work was rejected by other browsers because to implement those APIs correctly required you to architect your browser in much the same way as Chrome.
For this reason, the W3C and other standardization forums require at least two independent implementations of a technology to ratify it as a standard: multiple implementations would help clarify where the specification is unclear, but having independent implementations also informs the standardization process on if the architecture is too specific to a particular implementation.