3 ms·
That's amazing. Thanks for reminding me how much contempt they have for choice.
by smrtinsert 11y ago
That's amazing. Thanks for reminding me how much contempt they have for choice.
- dredmorbius 11y agoNot quite my area of expertise, but I believe that browsers on Android also tend to use the core Android browser components though they can dress them up slightly differently.
- lorenzhs 11y agoThey can, but they don't have to. Mozilla ships a Gecko engine in Firefox for Android.
- Someone1234 11y agoBrowsers on Android are not required to use Android's built in WebViews. And several alternative browser engines are offered by the platform[0]. Android has no specific restrictions in place. Although it is the path of least resistance to use the built in WebView, since you now don't need to deploy your own. [0] Including: Blink (Amazon Silk, Chrome, Opera), WebKit (BlackBerry, Dolphin, et al), Gecko (Firefox, Minimo), NetFront (Blazer). At the moment WebKit derivatives seem to be most popular, but several browsers re-build it from the source rather than just using Android's WebKit components.
- dredmorbius 11y agoThanks, as I said, NMAOE and I was mostly reflecting observations based on some dated Android builds.
- glogla 11y agoSome browsers do, but Firefox Mobile uses it's own core. That makes it possible to use extensions like ublock, for much better browsing experience than any browser without ad blocker can provide.
- sangnoir 11y ago> ...I believe that browsers on Android also tend to use... The word 'also' doesn't belong here. Browsers on iOS don't tend to use core iOS components (WebView) : they are forced to. Your statement really isn't a counter point.
- mcintyre1994 11y agoThey might tend to, but Firefox for example is the real thing on Android.
- dredmorbius 11y agoAh, I wasn't aware of that. Thanks.