Re:Current state of AV1 codec playback support – Oct '22
by paulryanrogers on Friday October 21, 2022 @07:00PM
(#33293871)
Locking the rendering engine blocks a host of capabilities, both for the browser itself and its ability to support 3P extensions
Re:Current state of AV1 codec playback support – Oct '22
by alwillis on Friday October 21, 2022 @08:28PM
(#33294408)
I doubt it. Safari has 3rd party extensions on iOS and WebKit has all of the important web platform features… in fact, it has pulled ahead of Chrome.
What Apple is avoiding is all of the security issues attempting to support multiple web engines.
Re:Current state of AV1 codec playback support – Oct '22
by brokenmachine on Monday October 24, 2022 @12:33AM
(#33312954)
Not an Apple guy, but I thought adblocking was not as good on Safari.
iOS supports changing the default browser to something that’s not Safari.
It’s not only about the rendering engines; Brave on iOS has other features and a UI/UX that I like that’s not present in Safari.
3rd party browsers on iOS have other ways of differentiating themselves, especially if you use those browsers on other platforms, like bookmark syncing, etc.
90% of end-users couldn’t care less what’s being used to render their websites on iOS.