Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

"about to be fixed" is pretty clickbaity with no substance.

From the July TC39 meeting [0]:

> After 7 years, Temporal is close to done. Our only focus is making sure in-progress implementations are successful, by fixing corner-case bugs found by implementors, and making editorial changes to improve clarity and simplicity.

It's not (yet) on the October TC39 agenda [1].

The Chromium implementation issue hasn't been updated since 2022. [2]

Webkit's implementation issue was updated once this year... to add a blocker [3]

V8 is passing 75% of test262's tests, and JavascriptCore is passing 41%. Spidermonkey is a no-show. [4] Note that test262 is incomplete and hasn't seen activity this year [5], so those percentages may decrease over time.

"about to be fixed" ehhhh. If it lands this year I'd be surprised.

   [0] https://ptomato.name/talks/tc39-2024-07/#2
   [1] https://github.com/tc39/agendas/blob/main/2024/10.md
   [2] https://chromestatus.com/feature/5668291307634688
   [3] https://bugs.webkit.org/show_activity.cgi?id=223166
   [4] https://test262.fyi/#|v8,v8_exp,jsc,jsc_exp,sm,sm_exp
   [5] https://github.com/tc39/test262/issues/3002


Yeah, I’ve been waiting for this for years and not optimistic it’s “near”.

The polyfill is too heavy and the services we deal with seem to cover the whole range of dates and times. Julian, epoch, ISO-8601.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: