Comment on FF Evangelists
Cris_Color@lemmy.world 7 months agoWhy would being WebKit based make it bad? Because it supports the web engine duopoly?
Comment on FF Evangelists
Cris_Color@lemmy.world 7 months agoWhy would being WebKit based make it bad? Because it supports the web engine duopoly?
FlyingSquid@lemmy.world 7 months ago
On an iPhone in specific it means there’s no real difference between them beyond mostly the cosmetic. It’s not just that it’s WebKit, it’s that it’s WebKit that’s also behind Apple’s walled garden.
Firefox that doesn’t render with gecko isn’t really Firefox, is it? I mean I get that Mozilla endorses the app, but it’s not the same Firefox as it would be almost anywhere else.
SkyeHarith@lemmy.world 7 months ago
As I mentioned above, it’s quite snappier than safari and even Firefox. It’s clear that they’ve worked on performance.
FlyingSquid@lemmy.world 7 months ago
That’s not my point. My point is that all iOS browsers are essentially the same browser because they’re forced to be.
SkyeHarith@lemmy.world 7 months ago
I agree. The recent EU ruling has atleast fixed that problem for EU citizens while the rest of the world catches up.
We were however discussing browsers in the context of desktops in the original thread. On MacOS, other engines are allowed.
Your issue is with apple’s draconian policy on ios, not webkit.
Further, two F1 cars using the same engine can perform vastly differently depending on how they’re tuned and how the car is built. While I do concur that it is criminal to not let us strap a jet engine to the f1 car, doesn’t mean that there aren’t differences between the currently legal cars beyond the coat of paint.