There are exactly three browser engines of any note: Safari's, Chrome's and Firefox's.
iOS allows other browsers and doesn't allow other engines. And considering things like this: https://webapicontroversy.com/ I'm not entirely sure I want Chrome anywhere near my phone.
>I'm not entirely sure I want Chrome anywhere near my phone
There are more browsers that use Chromium engine and nobody forces you to install Google version. I understand the potential issue of a Chrome dominance but Apple could listen for actual developers want and implement those features then you will no longer be forced to use an inferior browser.
> but Apple could listen for actual developers want and implement those features
Did you even visit the link? Developers may want the moon. And yet both Mozilla and Apple consider those (and not only those) harmful for a bunch of reasons, the primary of which is privacy.
Apple could be smart and implement what real developers need and not what advertisers want. But good performance, and better APIs would mean you could avoid using native apps.
Once again: real developers may want a lot of things. I've seen developers want bluetooth and location APIs in the browser. And yet, both Apple and Mozilla (note: not just Apple) consider these APIs harmful as currently presented and specified and haven't found/can't find a way to implement them in a non-harmful way.
And these APIs are the most visible. There are many other APIs and features that don't make their way into WebKit not because Apple "doesn't listen to real developers", but because the specs are extremely poorly written, or contain known bugs, or can't be implemented efficiently, or...
The scary thing is, these days Firefox devs are increasingly often on WebKit's side (because whatever your opinion of Apple is, WebKit devs want the same thing that Firefox devs want: a safer web web for people with properly implemented features). Whereas Chrome just plows through (because Google's raison d'etre is the Web, and Google wants to subsume and replace the web with all things Google).
You will also find (if you only cared about this) that standards that Mozilla considers harmful (or at least thinks they have to be deferred) are mostly aligned with Apple's: https://mozilla.github.io/standards-positions/
>Just as camera and mic location access is hidden behind a specific permission dialog in case you didn't notice.
Of course I know, the hypocrisy is that you trust your grandma with the camera permissions but not with a permission for a music player to run when the screen is turned off or with a map/fitness tracking page to get access to your location. If Apple devs would be competent they could implement it in a secure way like the camera API (or maybe the devs are competent and the reasons not to do it are financial)
Dude, Safari is worse then Firefox, stop showing the USB example. Anyway screw this, Microsoft was foprced to show a browser choice screen and Apple will be forced to show the same, it will take a few years but tit will happen. If you are not in EU you will not be affected at all. Since US will still use the inferior browser still all websites will have to code for it and native apps will have to be made to workaround the limitations.
> the hypocrisy is that you trust your grandma with the camera permissions but not with a permission for a music player to run when the screen is turned off or with a map/fitness tracking page to get access to your location.
Ah, the tired old "your grandma" "argument".
> Dude, Safari is worse then Firefox, stop showing the USB example.
Yes, I know. "Apple bad, Safari bad" and no amount of evidence that both Safari and Firefox resist multiple standards forced by Google will convince you otherwise.
You're so blind to your own bias that you didn't even see that I never mentioned USB even once (even though it is one of "considered harmful by both Firefox and Safari").
Think of the grandma is the Apple fanboys defense of why shit should be locked and approved by Apple.
You are mentioning location APIs and I shown you that is not different then camera APIs and then you still show me the bluttoh/usb stuff. https://www.safari-is-the-new-ie.com
You are trying to defend something I did not ask you about, I don't care is f Safari will never implement JavaScript at all, or if they decide grandma can't be trusted with camera permissions, as long you can install a better browser that gives you access to better APIs.
I also mention for APIs that could let you make a competitive streaming app based in the browser, this is not about USB,bluetooth, VR or other APIs, so try fucking focusing on why you can't have a good music playuer in the browser? Is it impossible by the laws of nature to create such an API? or are the Apple devs incapable of implementing such an API in a safe way? or Apple users too stupid to give permissions , or maybe Apple wants money and a streaming service that is browser based means no tax ?
Yeah, Apple is perfect , Google Siri search for all the times Apple lost in justice class lawsuits and practice on those cases how Apple was not screwing those guys and the justice was wrong and "Apple goog, Apple good ..."
btw are you a Trump fanboy, you are talking a lot in his style.
There are exactly three browser engines of any note: Safari's, Chrome's and Firefox's.
iOS allows other browsers and doesn't allow other engines. And considering things like this: https://webapicontroversy.com/ I'm not entirely sure I want Chrome anywhere near my phone.