On 19.10.2009, at 11:24, Joran Greef wrote:
>
> Thanks Tobie.
>
> Re: "...the unit of time measurement in Ruby is seconds, which
> explains the reason".
> Can we optimize for those familiar with Javascript? Is there any time-
> related API in Javascript which uses seconds?
Well, programmers ver
Thanks Tobie.
Re: "...the unit of time measurement in Ruby is seconds, which
explains the reason".
Can we optimize for those familiar with Javascript? Is there any time-
related API in Javascript which uses seconds?
Re: "Given ... the benefits of using seconds rather than milliseconds
in most bu
For the record, the unit of time measurement in Ruby is seconds, which
explains the reason behind that choice for Prototype.
Given the backwards compatibility issues, and the benefits of using
seconds rather than milliseconds in most but edge cases, there's litte
chance of seeing that change.
Be
"Units Of Measurement Options Stated Using Lowest Common Denominator
Unit Practical" -> +1 for most awkward title.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Prototype: Core" group.
To post to this group, send e
I, for one, found the units used by Function#delay (for example) to be
very surprising when I first saw them, and I have to stop and think
every time I use Function#delay. The usual unit for that sort of
thing in every language I've worked in other than BASIC is
milliseconds.
That said, I don't
Joran,
The type of number extensions you described aren't part of prototype.
Therefore, it is simpler for developers who aren't using such an
extension to use seconds. I'm not opposed to the switch, but I wanted
to throw out a possible explanation for the way it is today.
Allen Madsen
http://www
