Firefox must obviously be the core product, the one that people know, love and trust and can easily use - although this doesn't mean that Mozilla can't try othe

Firefox must obviously be the core product, the one that people know, love and trust and can easily use - although this doesn't mean that Mozilla can't try other projects as well, maybe with with more constrained resources so projects that don't get enough momentum don't linger for too long. And the writer has a point when he says that the weight of Firefox has allowed Mozilla to be a heavyweight at the table of the standards of the web. But there's a point he misses (and he was nearly there when he mentioned Gecko). What do Chrome, Safari, Brave, Vivaldi, Opera, Edge and basically every browser on Android and iOS have in common? That's the web engine - and that's WebKit/Blink, with Chromium usually being the foundation. That wasn't a big problem when the guys at Google were still pushing for better web standards, but that's no longer the case. Gecko may have a big window to become a really modular engine that any browser can use on any platform, and it could advertise itself like the modular, corporate-free, privacy-aware, fully standard-compliant solution that can power the next generation of browsers out there - or at least be an alternative to the WebKit/Blink/Chromium monopoly. I know that a while ago Mozilla had considered exposing Gecko as a browser-agnostic engine, but at some point for some reason they dropped the plan - and that's quite a shame.