Prev: JS charting library that can do bar charts from series of time "mm:ss" strings?
Next: How to count elements of a string
From: Ry Nohryb on 28 Jun 2010 09:59 On Jun 28, 3:54 pm, Thomas 'PointedEars' Lahn <PointedE...(a)web.de> wrote: > (...) > You miss the point. It is not necessary for the system clock of a computer > to use local time in order for the operating system to display local time.. > Not even in Germany, which you claim to know so well (but in fact haven't > got the slightest clue about). (...) JFTR: Pointy is austrian, not german. Isn't it, Pointy ? -- Jorge.
From: Ry Nohryb on 28 Jun 2010 10:12
On Jun 28, 3:54 pm, Thomas 'PointedEars' Lahn <PointedE...(a)web.de> wrote: > > (...) Mozilla-based ones will not go below 10 milliseconds > AISB (...) Yes. I wrote this to test that: http://jorgechamorro.com/cljs/097/ My findings (on an intel Mac): - Opera triggers faster a setInterval(f,1) than a setInterval(f,0). - Mozillas and Safari max out @ ~100Hz no matter what (0 ... 10) ms. - Chrome at 0..5ms gives 230Hz. - iCab comparatively flies: a setInterval(f,0) runs at more than 2KHz. -- Jorge. |