[no_wizard]

I wish someone from Mozilla or MS would comment on this, to be honest. Were they even considered?

Historically, I've heard from various sources that Mozilla may not work at the same pace as some of the large corporations do in upstreaming patches and releases to the code base. This has (according to what I have heard, which may simply rest on rumor/speculation/heresey, mind you) kept a lot of large entities from getting on board.

I've also heard that in building Quantum this is less of an issue, but their code base is a mess, and chromium's is incredibly well documented and clean by comparison.

Anecdotally, I would be inclined to agree with my second statement up front, after just browsing the two, but please compare for yourself

https://github.com/chromium/chromium

https://github.com/mozilla/gecko-dev

[snek]

microsoft switched to chromium because they want better control/integration with electron apps and the windows store. firefox wasn't on the table for them.

[no_wizard]

I really don't think this is it, if I'm being completely frank, because they already have an enormous amount of up front work done with making Windows PWA friend:

https://developer.microsoft.com/en-us/windows/pwa

I also am willing to surmise that they are going to put in alot of work re-working all their APIs that are exposed as Edge based interfaces into whatever engine they and up with here (namely chromium), so I don't think it would have been beyond them to put in the work to do something like they did with node and chakra core:

https://github.com/nodejs/node-chakracore

(which, btw, for now isn't dead: https://github.com/Microsoft/ChakraCore/issues/5865 likely for the reasoning I mentioned above)

I just don't buy it. I don't think easy electron compatibility is the main drive here.

[snek]

This was the reason I was given from a dev on the edge team. Do with that what you will.