Google is heading for a world of hurt with their internal web framework decisions as of late. They've been spinning their wheels for years trying to reinvent Wiz, and it's not going well.
I'm sure they've wasted literally billions of dollars in salary and opportunity costs. And in the end they're building multiple incompatible proprietary systems, with seemingly no checks on the team in charge of this effort. Even if they manage to succeed somehow, they'll have a system that no new hire will know, that doesn't have any external ecosystem, and definitely, that doesn't attract up-and-coming talent that wants experience that applies to the rest of the industry.
Funny enough, one of the new forks of Wiz can't use components from the other fork of Wiz, but _could_ use web components, because web components work anywhere HTML does.
So MWC actually was their only viable option for Material Design components. I think the Wiz team was desperately trying to find or fund another option because of how bad the managers thought this looked. Maybe you can't get a promotion embracing interoperability.
I'm sure they've wasted literally billions of dollars in salary and opportunity costs. And in the end they're building multiple incompatible proprietary systems, with seemingly no checks on the team in charge of this effort. Even if they manage to succeed somehow, they'll have a system that no new hire will know, that doesn't have any external ecosystem, and definitely, that doesn't attract up-and-coming talent that wants experience that applies to the rest of the industry.