![]() Sometimes the resources needed to support multiple platforms are not worth the benefit. Sometimes these limitations are temporary and caused by constraints in budget. Could Chrome support the methods of streaming that Apple used? Also yes. Could Apple also provide a stream that worked in Chrome? Of course they could. Simply because Apple used a method of streaming that Chrome did not support. For years the Apple keynotes were only available in Safari. Anyways, it now also runs on Safari.īut it also happens the other way around. The Google Earth team worked around that, or the Safari engineers improved their WebGL implementation. And I’ve very publicly called them out on this, but the reality was that Google Earth used some WebGL features that Safari did not support. So while they went with a standards-based approach, it was at first very much a side-step and not an improvement. It initially only worked in Chromium browsers. We’ve seen this happen with the Google Earth site a couple of years ago when Google replaced their Chrome-only NaCl implementation with a WebAssembly based one. It happens today and will likely continue to happen when Chromium-based browsers are allowed in the App Store. Or maybe the workaround would be less performant or less ideal in some other way. Perhaps it would just take some more time from the developers. What if the website could have worked around that requirement. And it is the choice of your browser to support it or not.īut what if that dependency on that web platform feature is not a hard requirement. If your browser does not support WebBluetooth, the website will not work in your browser. During the last couple of years, I’ve built many demos that require WebBluetooth. The issue could be that the browser you are using does not support the web platform features that the website is using. There may be some good reasons why developers and websites tell users to use another browser. And I think it would be a mistake to generalize here and say that every instance is completely and totally bad. I can tell this is a genuine worry, but I hardly think this is as black and white as they make it out to be.įirst of all, we need to consider why developers would do this. We want more voices everywhere, also on iOS.īut is there some truth to this, maybe? Are we fighting for more choice and inadvertently ending up having to choose between Chromium or Chromium?ĭevelopers will develop for Chrome and tell users to install Chrome. I just don’t think iOS is an exception to this. I do want more voices that is precisely what this is about. I do agree with Jen about the second part. And also a little insulting for the Safari team because why do you think Chromium-based browsers will suddenly overrun Safari? Are you saying Safari is not good enough? Jen Simmonsīut that argument seems weird to me. Nick LockwoodĮven Jen Simmons, an evangelist for the web developer experience team at Apple, mirrored that response by saying:ĭo we really want to live in a 95% Chromium browser world? That would be a horrible future for the web. ![]() Web developers don’t mind there being an engine monoculture, they just want it to be a Blink monoculture instead of a Webkit monoculture. And if we allow Chromium on iOS, WebKit will be doomed, and we will end up with Chromium everywhere. Apparently, iOS is the last bastion of WebKit that can prevent a Chromium monoculture. And last year, the British CMA published a preliminary report which may result in rules being imposed on Apple to force them to allow other rendering engines.īut I’ve also seen some responses that argue that having less choice is good for users. I’ve written about this before and why this is a problem.Įven some market regulators have picked up on this sentiment. ![]() The App Store rules force browsers on iOS to use the same rendering engine as Safari instead of using their own, as they do on every other platform, including macOS. Lately, web developers have begun to question Apple’s monopoly over browser rendering engines on iOS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |