Temporal: Getting started with JavaScript's new date time API

Re:Temporal: Getting started with JavaScript's new date time... by dstick on Monday June 28, 2021 @11:23AM (#27663100)

That's only half the story. It's "deprecated" because it's done. There's nothing more to add, fix or improve in the eyes of the maintainer. What a nice place to end up in:

_"We now generally consider Moment to be a legacy project in maintenance mode. It is not dead, but it is indeed done."_

https://momentjs.com/docs/

[ Parent | on HN ]

Re:Temporal: Getting started with JavaScript's new date time... by paxys on Monday June 28, 2021 @12:00PM (#27663564)

You skipped the line right after this which completely changed the meaning:

> We recognize that many existing projects may continue to use Moment, but we would like to discourage Moment from being used in new projects going forward.

[ Parent | on HN ]

Re:Temporal: Getting started with JavaScript's new date time... by dstick on Monday June 28, 2021 @01:41PM (#27664910)

Fair enough, but the parent mentioned that without quoting this part. So I just posted the other half. Regardless, you’re right - new projects shouldn’t use it because of unknown future problems.

[ Parent | on HN ]

Re:Temporal: Getting started with JavaScript's new date time... by rendall on Monday June 28, 2021 @12:20PM (#27663851)

> There's nothing more to add, fix or improve in the eyes of the maintainer. What a nice place to end up in

What a strange thing to say. Baffling.

It's deprecated because programming standards have changed, the team agrees with those standards and nevertheless feels it would be too much work to incorporate them. Not "there's nothing more to add" but "we choose to prioritize stability over new features"

[ Parent | on HN ]

Re:Temporal: Getting started with JavaScript's new date time... by blowski on Monday June 28, 2021 @11:42AM (#27663338)

Wow! Next time someone says "no piece of software is ever finished" I'll know where to send them.

[ Parent | on HN ]