How would replacing HTTP with SPDY offset Mozilla? It's not a threat. NaCL? NaCL is a different applet sandboxing, again not a threat to the browser or Mozilla. Dart? Dart is an alternative webpage scripting language (an alternative to Javascript).
Each of these does not threaten the importance of the browser. On the contrary, they both widen the use cases of the browser and raise the entry barrier for competing browsers. These effects protect Mozilla, instead of threatening Mozilla.
On the other hand, Google pushes OAuth single sign-on against Google accounts, whereas Mozilla is pushing Mozilla Persona, a distributed, no-central-authority SSO for the web.
I conclude the exact opposite of what you state. If we use Chrome, we're locked into technologies that serve Google, if we use Firefox we're pushing open technologies.
Each of these does not threaten the importance of the browser. On the contrary, they both widen the use cases of the browser and raise the entry barrier for competing browsers. These effects protect Mozilla, instead of threatening Mozilla.
On the other hand, Google pushes OAuth single sign-on against Google accounts, whereas Mozilla is pushing Mozilla Persona, a distributed, no-central-authority SSO for the web.
I conclude the exact opposite of what you state. If we use Chrome, we're locked into technologies that serve Google, if we use Firefox we're pushing open technologies.