For 99.99% of people the browser is not the renderer, it is the skin and all that comes with it (synced history, bookmarks, adblocking etc etc).
For 99.99% of people the browser is not the renderer, it is the skin and all that comes with it (synced history, bookmarks, adblocking etc etc).
(Disclosure: I work for Google, speaking only for myself)
Similarly if my Chevy has the exact same engine as a model of Dodge I would never say I’m driving a Dodge.
I don't see how this means that Firefox without Gecko isn't a browser. I can see how you might take issue with calling it Firefox, but it's clearly a browser that's in the app store.
I could see both sides, but ultimately I use Firefox as an attempt to try and keep chromium's monopoly as a web renderer at bay, even if for seconds longer. Firefox on IOS being forced to basically be built on top of a chromium engine defeats that purpose.
It's for similar reasons that I don't recognize "Visual Studio for Mac" as VS, but a rebranded Xamarin. It lacks several core features of VS that devs hearing the name would expect (let alone hundreds of more specialized features).
If you put a Dodge engine in a Chevy, you don't call it a Dodge, you call it a Frankenstein's monster which isn't either one and both Dodge and Chevy fans (but especially Chevy fans) will think less of you for it.
If anything this seems to me like an argument why Firefox with a Safari rendering engine is indeed a browser on the app store.
If a Telsa with a Honda engine is a car, why isn't Firefox with WebKit (which is what Safari uses) as it's rendering engine a browser?
You could argue it's not "real" Firefox, and I might see where your coming from, but my comment was specifically addressing the claim it's not a browser.