I would guess that Microsoft would keep using Chorus rather than adopting V8, but if they aren’t, then V8 has contributions from eg. Node.js
And as states in the article: Edge on Android and on ARM seems to already be Chromium based
I would guess that Microsoft would keep using Chorus rather than adopting V8, but if they aren’t, then V8 has contributions from eg. Node.js
And as states in the article: Edge on Android and on ARM seems to already be Chromium based
What I'm effectively asking is this:
1. If Google opts to steer Chromium in a way that the community finds objectionable, could the community stop it?
2. If the community opts to steer Chromium in a way that Google finds objectionable, could Google stop it?
The answer to that is obvious. Of course not.
Google owns Chromium's repository. Even if the "community" decides to fork Chromium, Google owns Chrome, so any fork of Chromium is completely irrelevant. That's because people download and install Chrome and not obscure Chromium forks.
And that is why web standards are important ;-)
Remember: Chromium itself is an “obscure fork” of WebKit...
Yes, exactly like those two.
>> "Remember: Chromium itself is an “obscure fork” of WebKit..."
Actually when Google forked WebKit, Chrome wasn't obscure at all. But yes, that's the perfect proof that Google doesn't want to cooperate when they aren't pulling the strings.
First they switched their engine to Blink, then predictably after 3 years sold out to an obscure Chinese private equity fund.
2. Yes.
Overall, it doesn't feel like there is a community at all, it's more like Google deciding everything then tell external contributors as a courtesy. I believe there can be technical influences driven by non-Google contributors but that's pretty rare.
That said, perhaps Microsoft can be an exception if their participation is big enough.