You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is more of a general question regarding your vision on the new Temporal API proposal and whether you are considering to start using it internally (similar to Intl.DateTimeFormat) in order to reduce the footprint even further as (and if) it gets adopted?
Or alternatively, where do you see that fit in? Would void some of the functionality? Do you recon the community should move towards a unified standard?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
This is more of a general question regarding your vision on the new Temporal API proposal and whether you are considering to start using it internally (similar to
Intl.DateTimeFormat
) in order to reduce the footprint even further as (and if) it gets adopted?Or alternatively, where do you see that fit in? Would void some of the functionality? Do you recon the community should move towards a unified standard?
I'm curious on your thoughts!
Beta Was this translation helpful? Give feedback.
All reactions