[citation][nom]esrever[/nom]All of them are the same since apple doesn't give developers any freedom.[/citation]
[citation][nom]ksampanna[/nom]I mean, c'mon ... bt obviously[/citation]
[citation][nom]LuckyDucky7[/nom]Was this review even necessary?There is no choice of browsers on iOS. None. Every "browser" is just a sub-par Safari wrapper.It's not like people buy iOS devices for the ability to tailor the device to their liking, after all- it's not called the "reality distortion field" for nothing.[/citation]
[citation][nom]cknobman[/nom]One of the biggest waste of time articles ever published on this site. WTF Toms?[/citation]
Not everybody is aware of what's going on with browsers on iOS. I've had people request this article, and I've also heard people say "I use browser X on my iDevice instead of Safari because it's faster." Before Nitro, I would have to agree with you, esrever, they were all the same. Not anymore. I think the fact that Apple continues to limit 3rd-party browsers to using the stock engines, yet has a new JS engine that only Safari can access is complete BS. And Nitro plays a big part in real-world usage that isn't easily seen on benchmarks that measure any one aspect, just look at and page load times. All iOS browsers are the same, right? Then how come Safari is the only one who can walk and chew gum at the same time? Nitro. If Apple kept the playing field level and they all were forced to use the same engines, they could always evenly compete on featureset, but with Nitro, the fix is in. The question is, how long can Apple keep this up while being the dominant player in the tablet sector?