Firefox

17890 readers

9 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 4 years ago

MODERATORS

[email protected]

Mozilla says Apple’s new browser rules are ‘as painful as possible’ for Firefox - The Verge (www.theverge.com)

submitted 9 months ago by [email protected] to c/[email protected]

43 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 0 points 9 months ago (3 children)

Wow, right up front, they're being disingenuous:

“The effect of this would be to force an independent browser like Firefox to build and maintain two separate browser implementations — a burden Apple themselves will not have to bear.”

...No? Apple won't bear that burden because they're going to keep using WebKit. Firefox can keep using WebKit. Not using WebKit is a choice, with pros and cons.

[–] [email protected] 0 points 9 months ago

Well maybe Apple shouldn't be so hostile to other browsers. Honestly I don't see why Firefox would bother will web kit. If they might as well not make a iversion.

[–] [email protected] 0 points 9 months ago (1 children)

Lol look at your downvotes!

[–] [email protected] 0 points 9 months ago (2 children)

He is right but people don't like the truth.

[–] [email protected] 0 points 9 months ago

Lol nope

[–] [email protected] 0 points 9 months ago

Lol look at your downvotes!

[–] [email protected] 0 points 9 months ago (1 children)

But then you read on and it says Apple is allowing the kit to not be used in the EU only. Outside of the EU, presumably, Firefox will still have to use the Webkit or whatever. So, while Apple uses its own engine in both the EU and the US on its phones, Firefox will be able to use its own engine in the EU, too, but will have to continue using Webkit in the US and other markets outside of the EU.

I'm not sure what disingenuous about that.

[–] [email protected] 0 points 9 months ago* (last edited 9 months ago) (2 children)

It’s disingenuous to act like this is some huge burden. You ship two browsers — one for the EU and one for other markets. Firefox already ships on a number of different platforms. Adding one branch isn’t going to kill them.

Or if it’s such a pain, you don’t bother and just ship the WebKit version everywhere.

[–] [email protected] 0 points 9 months ago

It’s disingenuous to act like this is some huge burden.

Having to double your software engineers, UI/UX designers, QA engineers, DevOps, and localization/accessibility specialists to handle a second browser is a HUGE burden for a non-profit.

If you don't care about quality, security, or user experience, sure you can just pass a "does it compile" test and push to prod. You'll quickly find that nobody wants to use this under resourced browser.

Or if it’s such a pain, you don’t bother and just ship the WebKit version everywhere.

This is exactly what Apple wants. They don't want to give people a real choice because they're scared of real competition.

[–] [email protected] 0 points 9 months ago (1 children)

Tbf, it would be a completely new & different browser from the ground up since they would have to make it from Gecko and such. And they are already struggling with their Android browser already.

But yeah, they could keep the WebKit version everywhere.

[–] [email protected] 0 points 9 months ago* (last edited 9 months ago) (1 children)

Would it be completely new and different? The only thing that changes is the rendering engine. The UI/windowing stays the same as the other iOS app. And the rendering engine has already been built for MacOS, so it’s not like they have to start from scratch — it’s the same base platform.

[–] [email protected] 0 points 9 months ago

Lol just a different rendering engine. So easy!