Ummmm, does it reload tabs like safari? Because Atomic Browser seems to have figured something out Apple hasn't...
Yes it does
Ummmm, does it reload tabs like safari? Because Atomic Browser seems to have figured something out Apple hasn't...
You do realise that's basically just a skin for Safari, right? Apple don't allow full alternative browsers on iOS. Even Chrome is just a wrapper around the default webkit ui
So all WebKit browsers are just skins now? Jeez the amount of ill-informed posts in this thread keeps on increasing.
He's not ill informed look up how browsers function on ios before you start trash talking other people.
I know how WebKit functions. I also know how a skin functions. Are you suggestion as well that the only difference between all the WebKit browsers is just the skin they paint on it? As you are basically saying that when Chrome used it, it was basically the same as safari? Just a different skin.....
Hmmm, really?
I know how WebKit functions. I also know how a skin functions. Are you suggestion as well that the only difference between all the WebKit browsers is just the skin they paint on it? As you are basically saying that when Chrome used it, it was basically the same as safari? Just a different skin.....
Hmmm, really?
"Apples App Store policies state: Apps that browse the web must use the iOS WebKit framework and WebKit Javascript.
"This means that web browsers cant implement their own rendering engines; they must embed a version of Safaris rendering engine. They cant offer a faster rendering engine or new web features. In effect, each third-party browser on iOS is a different interface around Safari."
http://www.howtogeek.com/184283/why...safari-on-iphone-and-ipad/?PageSpeed=noscript
I think part of the reason some people don't complain about it is because there's absolutely nothing we can do.
Apple will do what Apple does and we can't change it. We're just along for the ride, and both times I've looked over at the Android side I saw a less stable platform with MANY more issues than our scant few.
Do I wish the iPhone 6 series had more RAM? Yes. Can I do anything about it? No. Do I want to use Android, a less stable platform with four times as many bugs? No as well.
No. The fail is strong with that train of thought.
Fair enough if you think a browser is just a rendering engine with a skin.
Agreed and I never disputed that either. That is not what was being said nor discussed nor disputed.
"browsers are not allowed to implement features that preserve tabs when reloading..."
I missed that part.
Yes. That train of thought is full of fail. The alternative browsers on iOS kick Safari's behind all over the AppStore.
Despite quick reloads, for people with limited data plans it can be a potential issue depending on how much of a page is cache-able. Unnecessary data utilization is among one of the problems that excess reloading can cause (and not limited to Safari, but any apps, especially ones that rely on data) - point being that data usage is only one of the components that is necessary/triggered when this behavior occurs.
And true, software optimization can help - but you are then simply shifting the onus of relieving the problem elsewhere, assuming that's where the fault lies.
Saying that more RAM will fix a problem that most people don't think is a problem is akin to saying "my car sometimes stalls when it's running, why don't Ford put twice as much oil in!".
It's much worse on the iPad (Safari is basically unusable for more than a tab or two), but the lack of ram is still disappointing. iPhone 6S will almost be a mandatory upgrade
I can open three tabs in my iPad without reloading just fine. I find your comment mildly hyperbolic.
Ummmm, does it reload tabs like safari? Because Atomic Browser seems to have figured something out Apple hasn't...
I've actually tried atomic browser and it didn't have they reload issue. It's the only browser that doesn't have the issue and I tried all of them but the thing hasn't been updated in 2 years so I don't wanna use it.
If I recall correctly, Atomic Browser utilizes offline caching (e.g. Safari's Reading List feature), which offloads resources to disk, which can alleviate memory issues. I don't know whether Safari does it or not, but I'd hypothesize the latter, given that Apple added the Reading List feature.I've actually tried atomic browser and it didn't have they reload issue. It's the only browser that doesn't have the issue and I tried all of them but the thing hasn't been updated in 2 years so I don't wanna use it.
But what this tells me RAM is not the issue. It can be fixed in software. This whole RAM whinestorn is pointless.
But what this tells me RAM is not the issue. It can be fixed in software. This whole RAM whinestorn is pointless.