We, the Moment team, think you should use @luxonjs for new applications until GitHub.com/TC39/proposal-tem… is viable. RT and save your friends some pain?
Whenever I'm using Moment.js, I think to myself, "I see you. You are MUTABLE and I will not be fooled this time!!!!"
Aaaand inevitably, I'll end up with at least one bug that would've been prevented by immutability 🙄
Me, tonight, trying debug a Luxon issue by fiddling with my computer's time zone settings: this is clever
Me, five minutes later: how the FUCK did it get to be 4 am?
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.
Lotta Luxon activity to catch up on! We've released several new versions, bring us up to 1.19.2. Brief thread of what we've added or changed below, and what's next.
We made some small performance improvements, fixed a few odds and ends, cleaned up some tests and documentation, and just generally tried to get things in order.
Luxon has released 1.16.0, with a fix for...[complicated scenario involving locales, zones, and formatting tokens]. Just take my word that Luxon is better now
If you think the advantages of, say, date-fns, outweigh the advantages of using Luxon, you should absolutely, 100% use date-fns. I do not know why you would think I would care, and trying to jam a debate about it into my Github issues is obnoxious.