About the milliseconds I agree with you. It could have the same API like
setHours( hours [, minutes, seconds, mili-seconds] ) of date instance. I
didn't talked about Idea of doing it per instance since I don't know about
browsers and Nodejs implementations. That's why I need your opinion. But
abou
I’d love to have this use milliseconds rather than minutes, so that we could
kill two birds with one stone. For example, I currently have my own NTP
integration for a web project I run, and for that the offset from the actual
time could be quite small.
> On 29 Apr 2018, at 18:07, Isiah Meadows
I'd personally prefer this to be settable on the instance, rather than
the global object - you can manage universal dates more easily across
time zones this way, and it still enables developers to have the
fallback in case they need an escape or if they have code that relies
on time zones remaining
To clear things out, I don't mean any changes to the actual Date time of
Javascript. What I want to discuss about is a problem with a very simple
solution.
Issue: Since Javascript code is mainly executed on a device that you might
not have access to timezone and time settings that would be very h
4 matches
Mail list logo
