> Some argue that it's good to have an independent rendering engine. Here too Firefox plays no role at all. The only counter force to Google's web feature roadmap is Apple/Webkit, not Mozilla.
I'd like to understand this point better. Does Firefox use the Chromium engine under the hood?
Nope, Firefox still uses its own rendering engine and JavaScript engine—except on iOS, where it's essentially Safari with a UI wrapper. But that’s due to Apple’s ToS, not Firefox’s fault.
I assume the previous comment was about market share. It’s low, yes, but I still think Firefox has influence despite that. Having a third rendering engine is valuable—especially now, after Microsoft killed IE/Edge and turned it into a Chromium fork. The percentage might not be high, but the people who use Firefox are usually the ones pushing for keeping the web an open standard.
It doesn't use Chromium. I think that their point is that Firefox's rendering engine, Gecko, can only have an impact on the rendering engine space proportional to its user base, which they have argued is insignificant.
I'd like to understand this point better. Does Firefox use the Chromium engine under the hood?