Alexandre: I feel it's only *related* to dates and times:
- Dates and times refer to absolute points.
- Durations would refer to distances between two dates and/or times.
However, I do feel this should be discussed in
https://github.com/tc39/proposal-temporal. And down this vein, I've
created
Please take a look at https://github.com/tc39/proposal-temporal
On Mon, Mar 4, 2019 at 3:30 PM Mark Davis ☕️ wrote:
> Sadly, time is not that simple. Most people using calendars consider the
> duration between January 15 and March 15 to be exactly 2 months. But such
> intervals are a different
Sadly, time is not that simple. Most people using calendars consider the
duration between January 15 and March 15 to be exactly 2 months. But such
intervals are a different number of days, hence milliseconds.
Mark
On Mon, Mar 4, 2019 at 11:21 AM Naveen Chawla wrote:
> I don't like it.
Personally, I’d love to see something like this included as part of the
temporal proposal (https://github.com/tc39/proposal-temporal), as I’ve been
experimenting with something very much like this here:
https://github.com/rbuckton/temporal/blob/master/src/Duration.ts.
I think a Duration type
I don't like it. Duration is just milliseconds for me.
On Mon, 4 Mar 2019 at 18:47 Alexandre Morgaut
wrote:
> Here a proposal to make ECMAScript natively support a Duration Object
>
> I talked about it a long time ago (2011) on the WHATWG mailing list in the
> context of the Timers API:
>
Here a proposal to make ECMAScript natively support a Duration Object
I talked about it a long time ago (2011) on the WHATWG mailing list in the
context of the Timers API:
https://lists.w3.org/Archives/Public/public-whatwg-archive/2011Feb/0533.htm
l think that such a proposal would better take
6 matches
Mail list logo
