Would such a move away from Safari stop the iPad Air crashing problems? Pro's & con's?
From reading on here apparently chrome is just as crashy on iOS7. I know from when running iOS5 on my iPad with Chrome it never really had too many problems and it could operate about 20 tabs just fine, crashing rarely, not sure what the case is, but from here I think it's pretty crashy with Chrome too!
For me Chrome, Mercury and Atomic Web seem to be more stable than Safari. That is remarkable as they are all running on top of Safari. My guess and the keyword is guess is that Apple decided reloading tabs on Safari was a way to release memory. The devs on the other browsers evidently didn't set those priorities the same.
That is misinformation. Stop spreading it. Chrome is running a webView which is different than Safari. The javascripnengine is much slower in webViews and they have their own set of issues.
Would such a move away from Safari stop the iPad Air crashing problems? Pro's & con's?
Chrome is a free download, just try it for yourself.
http://stackoverflow.com/questions/11648184/uiwebview-and-safari-comparisonTo be specific: Apple mandates that any third-party Web browser sold in the App Store must use the stock WebKit rendering and JavaScript engines.
They are all WebKit browsers. And not just different WebKit browsers like Chrome and Safari on the desktop, either, but complete mobile Safari clones. Third-party iOS-based Web browsers are all Safari wearing different clothes. Some of them have totally different syncing features, bookmark mechanisms, on-screen keyboards, and even user interfaces. But when it comes to a Web browser's primary function of rendering Web pages, they are all just re-spins of Apple's stock, default mobile Safari. While Apple demands that third-party browsers use the stock engines, Safari has newer JavaScript engine, while the rest are left with Safari's old JS engine.
http://stackoverflow.com/questions/11648184/uiwebview-and-safari-comparison
They aren't the same. Again stop spreading misinformation. If Chrome and Safari were the same there would be no reason to use Chrome. Safari uses nitro Javascript engine. Chrome on iOS does not. That's why Safari is faster on iOS devices vs other browsers using stock webkit.
Obviously reading comprehension is not one of you skill sets. Try again.
To be specific: Apple mandates that any third-party Web browser sold in the App Store must use the stock WebKit rendering and JavaScript engines.
They are all WebKit browsers. And not just different WebKit browsers like Chrome and Safari on the desktop, either, but complete mobile Safari clones. Third-party iOS-based Web browsers are all Safari wearing different clothes. Some of them have totally different syncing features, bookmark mechanisms, on-screen keyboards, and even user interfaces. But when it comes to a Web browser's primary function of rendering Web pages, they are all just re-spins of Apple's stock, default mobile Safari. While Apple demands that third-party browsers use the stock engines, Safari has newer JavaScript engine, while the rest are left with Safari's old JS engine.
I think iOS Chrome is built on the same engine as Safari due to Apple app restrictions so I don't think it will crash less. I could be wrong though, wouldn't be the first time.