|
|
|
|
|
|
by shmerl
5252 days ago
|
|
|
Great, so they just know that there are more vulnerabilities in their own optimized engine, still they use it in their own browser. At the same time they ban anything else on the system, claiming that it promotes security. Doesn't sound convincing to me at all. Meaning, that if I, as user will find a more secure browser - I won't be able to use it, since it's banned on pretense that it'll compromise security (hypothetically, not that I use iOS as a user anyway). |
|
|
This is just an example of Apple releasing new code in the browser first before extending it into other apps being turned into an excuse for people to ignorantly or dishonestly bash Apple.
The reason it was put in Mobile Safari first is obvious-- Apple controls the source code there. Thus they can deal with any instability caused by the engine in the wild there.
If they immediately put it in all the UIWebViews in the system then many third party developers apps would become unstable due to these bugs.
I find it quite astounding that people are trying to make hay out of Apple using a phased roll out for a key piece of technology.
It just shows how any opportunity that can be used to mischaracterize Apple is seized upon, and even when the situation that led to the original issue is long resolved, people continue to report it as fact.