zlacker

[parent] [thread] 4 comments
1. parasu+(OP)[view] [source] 2023-01-24 13:57:19
Chrome and Firefox may use WebKit but have very different looks and feels and some different functionality. They’re not just “skins”.
replies(2): >>noblea+Wa >>sccxy+1D1
2. noblea+Wa[view] [source] 2023-01-24 14:49:59
>>parasu+(OP)
They use a Cocoa feature called [WkWebView] (https://developer.apple.com/documentation/webkit/wkwebview) which is an embedded webkit browser. Any functionality that differs from Safari is not part of the actual "browser". It's just "skin" on top of it. (Bookmark syncing, etc)
replies(1): >>parasu+nm4
3. sccxy+1D1[view] [source] 2023-01-24 20:29:53
>>parasu+(OP)
Not really different. They even share bugs.

If Safari team messes up their rendering engine, then iOS update, and it is broken for every iOS browser...

replies(1): >>parasu+Pq5
◧◩
4. parasu+nm4[view] [source] [discussion] 2023-01-25 16:30:08
>>noblea+Wa
WkWebView is a web renderer and partial navigator, it's not a browser.

My point is that people are really stretching the term "skin". Bookmark syncing, tab & window management, history management, security management etc. all are features of a browser, and they have a major impact on the UX of that browser. They are WHY there are still users of Firefox or Chrome on iOS! They're not "skin" features, which typically imply minor look & feel related items.

◧◩
5. parasu+Pq5[view] [source] [discussion] 2023-01-25 21:28:15
>>sccxy+1D1
Do you use any of them regularly? I do. They're very different UX-wise.

My point is that users don't really care about the common rendering engine. It doesn't have much impact on the day to day UX.

[go to top]