You make it sound like Mozilla is somehow fighting against Google for the open web. But virtually all browser vendors are aligned on this issue, and have been working towards improving the web through standardization, improved performance, and functionality for years now.
The point of the article is that while Google is mostly aligned on the issue, Google also does things like creating PNaCl, which is not an aligned behavior.
(P)NaCl was introduced to replace NPAPI, at a time when the majority of rich web interaction still happened through plugins.
I'm glad to see it killed off, and have been expecting it for a few years now. JS/asm and (hopefully soon) WebAssembly have supplanted many of its features and benefits.
Still, this doesn't strike me as anti-open web. Google offered a solution when one was needed - it didn't gain traction, so they eventually retired it.
Google introduced PNaCl and made it available as a feature any Web page could use, knowing that there was effectively zero chance it would ever become a cross-browser Web standard. That was anti-open-Web.
And yet I can still only use Google Meet in Chrome. And many "standards" are only partially implemented in other browsers, or require browser-specific prefixes.
I'd also go so far as to say that Google's AMP project, as implemented, displays a distinct step away from an open web.
