Except Temporal is not, in fact, out.

The current global availability of native Temporal is 1.81%. For context, IE11(!) has a higher global usage than Temporal has native support. For my organization, this likely means we're years from being able to use Temporal in production, because getting the polyfills approved is such a hassle.

Keep in mind that even as of December last year, Chrome didn't ship with it yet (i.e. support is less than one month old). Safari still does not.

▲

senfiaj 11 hours ago | parent | next [-]

Chrome will ship in 144. It's about to release.

▲

winstonp 9 hours ago | parent [-]

Once Chrome does, for many devs, you can simply enforce a version check and say "please use latest Chrome" and be done with it.

	▲	promiseofbeans an hour ago \| parent [-]
		Please never do version checks. Test for the existence of the exact features/methods you need instead - this is trivial in JS: if(Temporal) Checking against version numbers helps cement existing browser monopolies, makes it difficult for new browsers to view websites (even if the browser correctly implements every feature), and encourages everyone to spoof version numbers / browser names which leads to them becoming a less and less useful signal. See any browser’s User-Agent string for an example of this

▲

10 hours ago | parent | prev | next [-]

[deleted]

▲

themafia 10 hours ago | parent | prev [-]

Thankfully temporal-polyfill only depends on temporal-spec. It was pretty easy to get that through.