News for hackers. Stuff that matters.
Re:Current state of AV1 codec playback support – Oct '22 by throwup on Thursday October 20, 2022 @08:49PM (#33282806)
The issue raised is not about video codecs, but about browsers. Apple is using their market position to artificially prevent Safari from being competed against by other vendors—that is classic antitrust behavior.

For comparison, imagine Microsoft banned all browser engines other than EdgeHTML from running on Windows. Would you find that acceptable?

Re:Current state of AV1 codec playback support – Oct '22 by MBCook on Thursday October 20, 2022 @08:53PM (#33282829)
This is an article about video codecs. I interpreted the above comments as complaining Safari was a problem for not supporting this video codec.

So my comment was about their video codec policy.

Re:Current state of AV1 codec playback support – Oct '22 by MobiusHorizons on Thursday October 20, 2022 @09:26PM (#33283112)
You may not be aware, but chrome does exist on iOS, but even so, it is actually running the safari rendering engine because apple prevents other browser engines from running. This effectively prevents chrome or Firefox from offering a browser with av1 support (as far as I am aware) so the browser engine is relevant to the codec policy discussion.
Re:Current state of AV1 codec playback support – Oct '22 by threeseed on Friday October 21, 2022 @12:08AM (#33284395)
I don't believe Apple has banned alternative engines.

It's just that they don't allow JIT code execution for security reasons which is needed for a comparatively performant engine.

Re:Current state of AV1 codec playback support – Oct '22 by Jasper_ on Friday October 21, 2022 @12:45AM (#33284607)
Yes, they have banned alternative engines.

https://developer.apple.com/app-store/review/guidelines/#2.5...

> Apps that browse the web must use the appropriate WebKit framework and WebKit Javascript.

Re:Current state of AV1 codec playback support – Oct '22 by enkrs on Friday October 21, 2022 @03:06AM (#33285336)
Which is the reason why I choose iOS: I trust Apple to implement the integrations in the WebView for best battery life. To get new OS features in the browser right away. Would Google Chrome implement picture-in-picture on the iPhone if they were running their own engine?

I use Firefox on iOS for the password and tab sync integration, and am supper happy that it’s using the WebKit framework. I care about the iOS experience more than some video codec support.

Re:Current state of AV1 codec playback support – Oct '22 by vetinari on Friday October 21, 2022 @04:04AM (#33285680)
If the other browsers could implement their engines, you would still have the option not to install them.

Since they can not do it, you don't have that option.

Re:Current state of AV1 codec playback support – Oct '22 by alwillis on Friday October 21, 2022 @04:29PM (#33292690)
If the other browsers could implement their engines, you would still have the option not to install them.

So it’s okay for user who (in theory) installed a 3rd party browser on iOS to have a worse experience and potentially make themselves vulnerable to malware? That’s exactly what Apple doesn’t want.

Re:Current state of AV1 codec playback support – Oct '22 by paulryanrogers on Friday October 21, 2022 @09:11PM (#33294696)
Or potentially offer a more secure browser than Safari
Re:Current state of AV1 codec playback support – Oct '22 by dmitriid on Friday October 21, 2022 @03:32AM (#33285491)
Given that Chrome abuses its market position to ram through and continuously release hundreds of Chrome-only non-standards I view this as a net positive.