Luxon.js

The Earth still refuses to orbit in a clean multiple of its own rotation, and don't get me started on the Moon, who is just off doing its own thing. The ticket to sort it all out has like a zillion upvotes but they just ignore my pull requests altogether.

Luxon 3.4.4 released, with the big addition of localized week and weekday support

@DasSurma A lot of people here have mentioned the tooling, which I agree is important. But I think Rust’s secret weapon is the safety. I remember from my Ruby days that dropping to C felt like a huge undertaking because I’d screw it up. But Rust let’s you build confidently

I’m kinda fascinated by how Rust was the harbinger of next-gen JS tooling. Why did it take Rust? There were “fast” languages before, so performance alone isn’t the reason. Is it the modern, cross-platform toolchain that makes it easy to install these new tools for users?

Advice needed. Let's say your team is full stack, and a talented, experienced engineer joins, but he's only done backend work. You want to train him up, everything from HTML/CSS to TS and React and all the toolchain craziness that comes with it. How? Is there, like, a book?

My number one date api request is to give me the offset in seconds instead of minutes

Luxon 3.4.0 is out!

The yearly dance of DSTs is always fun, for some definition of fun

Luxon 3.3.0 has been released, and it loves you.

Is that a git conflict marker or are you just a deeply nested generic type param?

Every time someone hassles me about not being adequately responsive on OSS work, I spend the next two days ignoring Github.

@jlongster I’ve used it quite heavily. It works well and does what it says. The challenge is that you can’t use it outside of React. I ended up wanting that and wishing I’d used Zustand instead

Has anyone used Jotai (github.com/pmndrs/jotai) and liked/disliked it?

Luxon security advisory: github.com/moment/luxon/s…

Luxon 3.2.0 released

Hi, it's Luxon, your friendly local datetime library, back from a nice offline break. How's everything been? Swell, I take it?

Luxon 3.0.4 released. Get it while it's still fresh from the oven, for extra delicious time and date functionality.

@duhdennie @AndreiGordeevSE @codepo8 Yes, document.getElementById.bind(document) works. But most people just wrap stuff like this in a closure

@luxonjs @AndreiGordeevSE @codepo8 could you .bind() it maybe?

...Christ

@duhdennie @AndreiGordeevSE @codepo8 The bigger difference is that the alias one doesn't work. In userland JS functions, you'll get an undefined `this` inside the method. For a native call like document.getElementId, they check this and throw an `illegal invocation` error

@AndreiGordeevSE @codepo8 yeah difference being that this one doesn’t have to traverse 2 calls

Luxon 2.5.0, 3.0.0, and 3.0.1 released in quick succession

Luxon 2.4.0, now with support for the ISO zone extension

So that's all to say that Luxon won't do anything more than add some toTemporal()-type adapter methods and ride into the sunset. If all goes well, in a few years, it will be a distant memory.

For Temporal, a date-fns-like library design makes a lot more sense. It has all the advantages of that approach but not the pain points it has with Date.

Some quick thoughts on the future of Luxon vis-a-vis Temporal