zlacker

[parent] [thread] 4 comments
1. Ashley+(OP)[view] [source] 2022-06-22 14:35:03
I think it's very unlikely that the web will end up Chromium-only.

macOS-specific browser share numbers are hard to come by, but on our own moderately sized website we see about 60% of macOS users choosing Safari. Even if iOS allows other browser engines, presumably a similarly large number of iOS users would also choose Safari, either because it's the default or because they like it. So regardless of what happens with iOS regulation, it seems likely there will always be significant Safari usage on the web.

So then the only way we end up with a Chromium-only web is firstly assuming a worst-case scenario for Firefox essentially falling out of use, but its usage on desktop appears to have stabilised around 7-8%. Secondly Apple would then need to decide to ditch WebKit for Chromium. I can't imagine they'll ever do that. Apple have a strong desire to do things their own way and keep full control over how their browser works. So I think we're a long way from a Chromium-only web.

replies(1): >>izacus+p
2. izacus+p[view] [source] 2022-06-22 14:36:35
>>Ashley+(OP)
If anything, I'd expect Safari share to grow since competition might kick Apple to improve their browser to be a true equivalent or better competitior to Chrome.
replies(1): >>solard+K
◧◩
3. solard+K[view] [source] [discussion] 2022-06-22 14:38:20
>>izacus+p
The opposite seems true right now, with Apple deciding to improve its proprietary ecosystems (app store, swift, etc.) and letting WebKit stagnate. There's a lot that Gecko and Blink can handle but Safari struggles with, seemingly by design. Apple doesn't want a strong web-based ecosystem because that means their competitors can use it too, vs the iOS/macOS only stuff.

If they wanted to, they could switch Safari to Blink just like everyone else did, but still keep adding features on top of it (privacy, iCloud integration, whatever), the same way Microsoft does.

No user asks for a different layout engine, that's corporations fighting with different values and priorities. The differentiating features for users are layers above that and arguably held back by renderer differentiation.

replies(1): >>Ashley+Sm
◧◩◪
4. Ashley+Sm[view] [source] [discussion] 2022-06-22 16:13:35
>>solard+K
Apple do appear to be trying a bit harder with Safari - since the regulatory heat has turned up, they've started releasing Safari more regularly since v15, and adding more new web platform features. Safari still does have its problems but I don't think it's fair to say Apple are letting WebKit stagnate.
replies(1): >>solard+2K1
◧◩◪◨
5. solard+2K1[view] [source] [discussion] 2022-06-22 23:26:45
>>Ashley+Sm
I don't know how you're quantifying "trying a bit harder", but from caniuse: https://caniuse.com/?compare=edge+102,firefox+101,chrome+102...

Safari and iOS mobile are the main outliers. Firefox is a little behind too, but few people use that anymore.

Chromium/Blink development is what actively drives the web forward, with everyone else playing catchup. Apple just doesn't care about that (or is perhaps purposely trying to slow it down) in favor of their own priorities and platforms.

[go to top]