Matt Johnson: The Past, Present, and Future of JavaScript Date and Time APIs | JSConf EU 2017

2017.jsconf.eu/...
JavaScript is notoriously bad when it comes to date and time problems. The built-in Date object has so many quirks and implementation differences that many developers have abandoned it, in favor of libraries. How did we get here, and what can be done about this? This talk is in three parts, and led by maintainers of the Moment.js library. First, you’ll understand how the Date object came to be, what parts of it are useful, and where the problems are. Next, you’ll learn about the present-day alternatives. We’ll cover three modern JavaScript libraries: Moment, date-fns, and js-joda, all of which are viable solutions. Lastly, you’ll hear about how we are working through the ECMAScript technical committee to get better support for dates, times and time zones built-in to the language.

[@nO_d3N1AL]

It never ceases to amaze me how it's so difficult to get Date and Time right. Tom Scott's video on this issue is worth watching too.

[@daltonjohnson6620]

Thats my dad! Great video.

[@ahmarsiddiqui]

good talk

[@consciousmi4842]

What would be the solution to first issue? Selects a date, but shows different date.

[@AkxeOne]

I might be the only one, but when it comes to date, I take it as an Object, therefor mutable. This kind of thing goes trough out the whole javascript, and I think it should stay there. There ain't a thing stoping you from cloning the object and replacing its occurrence, but mutability is a great concept as well.