4 ms·

Looking at the caniuse results... f*king Safari (and Opera)... https://caniuse.com/temporal https://caniuse.com/temporal

• agos 7mo ago
  I usually am not too harsh on Safari on implementation of new features but this is a bummer, and reflects poorly on them
• beezlewax 7mo ago
  And I have to support safari while dealing with all the problems that are mentioned in this article. Maybe there is a polyfill.
  • jitl 7mo ago
    yes, there's a few different polyfills https://github.com/tc39/proposal-temporal/tree/main/#polyfills https://github.com/tc39/proposal-temporal/tree/main/#polyfil...
  • tracker1 7mo ago
    Probably, but I'm guessing it's as big as moment.js ...
• dmix 7mo ago
  there's plenty of polyfills for every new JS idea on the roadmap
  • tracker1 7mo ago
    Maybe, but it's probably the size of momentjs for Temporal and likely still not quite right. It's also not fun at all to have to target a bunch of fills/shims for a specific browser subset, though if you're targeting mobile, you kind of have to target Safari. Not as bad as IE of old, but still seems to similarly be the odd one out always lagging half a year or more behind.
• deleted 7mo ago
  [deleted]
• jitl 7mo ago
  They've been working on support for a while (years), eg this 2022 commit. https://github.com/WebKit/WebKit/commit/e6717cdeb6a841f4b1f6b9d8d3b0dec947850abe https://github.com/WebKit/WebKit/commit/e6717cdeb6a841f4b1f6... perhaps don't be hard on them, Chrome released this to stable 2 months ago.