XPost: comp.sys.mac.advocacy, misc.phone.mobile.iphone
From: nospam@nospam.invalid
In article , Bob
Campbell wrote:
> >
> > what possible benefit is there for an end user to know the
> > instantaneous refresh rate of the display, as it constantly changes
> > based on the currently content, as well as various other factors
> > (finger motion, power management, thermals, etc.)?
>
> None, of course. Itıs only important to Kiddie Trolls because itıs
> ³something you can do on Android but not on iOS².
>
> As if.
>
> What the Kiddie Trolls fail to understand is that iPhones are not aimed at
> computer geeks. Nor are iPads. Actually the Kiddie Trolls fail to
> understand LOTS of things. But I digress.
>
> iPhones/iPads etc. appeal to non-geeks and non-nerds precisely because all
> the gory details are hidden. You turn it on and It Works. Thatıs it.
>
> Since 8 of the top 10 selling phones last year were iPhones, I would say
> that Apple is on the right track with this.
if only they had real-time readout of the refresh rate, they would have
had all 10!
> > a very bored app developer could write an app that queried and
> > displayed that value, although that won't actually be of much use for
> > one very obvious reason (which i doubt the usual suspects will figure
> > out).
>
> Since I am not a clueless Kiddie Troll - and have 40 years of programming
> experience in multiple languages - yes the reason is obvious. The very
> act of displaying this info, say in a tachometer-style round gauge with a
> needle moving around showing the refresh rate - is going to affect the
> refresh rate.
good guess. but actually that's not why :)
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
