Doesn't that kind of miss the point that the Germans are still deceiving people about the car's performance (aka a "trick")? -This governing of the experience is only part of the issue at play with the browser issue. This "trick" Safari uses also serves a latent purpose of hiding something they think people do not want- namely seeing the unfinished tiles. This would be like the German sports cars being throttled, and it also just happens to be the case that they shake really bad, or make a loud noise when operated above 150 MPH, so the manufacturers govern the top speed. Likewise, Apple is governing the way the browser populates the page because of the "unpleasant" experience that may result. My point is that you can call it whatever you want, whether sought after or intentional or not, the hiding of capabilities is still a deception (especially if chosen to be hidden). And the worse part is that yes, the deception is a choice, but (until the Maven browser) it was not one YOU could make, it was made for you.But, sm.knipe, you miss the point...Maven proves that iOS browser way of doing things is NOT because of some technicality limitation, but because that is how Apple feel is the right speed for their customers. It is like most German sports cars limit their top speed to 150 mph...most can get above this speed without harm...but Germans chose to put this limit (which is defeatable with software). It is just a matter of taste that Apple does this. Thus, it is NOT a "trick" to smooth out the browser...it is by CHOICE. In other words, if Apple chooses to make a quick scrolling browser, then i am sure that it can do so smoothly without difficulty since there is nothing technically limiting them. (Maven browser proves that this CAN be done on iOS. But apparently, Apple engineers like their method better.)
Upvote
0