Justin Searls: [00:11:51.19] Yeah, so - I mean, John’s overall story… And it was unusual to anyone who reads his blog. And I’ve been reading it – it was actually maybe the first blog I started reading once I first used a Mac. I had a job, I got an iMac G4, which was the cool one that looks like the Luxo Jr… And my boss said, “Alright, so here’s some keyboard shortcuts, and go read Daring Fireball every day.” I took those as marching orders, and I’ve been reading John’s blog ever since. And while we’ve never interacted outside of a couple of emails here and there, it’s extremely unusual for him to share a strong editorial opinion in one of his non-link blog, as in it’s just a post on his site that doesn’t link out to something else. Extremely unusual for him to share in an editorial format anything critical of Apple that doesn’t have a heavy counterweight.

And what this was basically saying is like “Look…” He starts – well, I guess the counterweight was he starts by saying “I blew it. I should have seen this coming. We shouldn’t be surprised that Apple announced the delay of these more advanced Apple Intelligence features like the personalized context, and the semantic index”, and all the stuff in the really, really impressive, that we talked about on this show a year ago –

Daniel Ehrenberg: Well, unfortunately, the team maintaining the polyfill has been really focused on the needs for it in a kind of specification context to just be completely correct, rather than being totally production ready. And ultimately - yeah, maybe we would have to ship the timezone database anyway if we wanted to – well, we could be like Luxon and use the Intl.DateTimeFormat for that.

Anyway, there’s a lot of messy decisions that you have to make when making a date/time library really production-ready. And we know how to do that engineering work kind of generally, but it just hasn’t been done. But this is an opportunity for contributions. The polyfill that was written by the proposal authors is there, it’s open source; I will have a link to it in the show comments. And people there would love to have contributors work on productionizing it, and are happy to mentor folks to do so.

Jerod Santo: Quick, real-time follow-up - the thought I was having about Moment actually is Luxon, and team [unintelligible 00:28:13.20] helped putting the dots together… And you mentioned Luxon, Divya; that is actually written by one of Moment’s maintainers, and is kind of like a lighter-weight thing.