News for hackers. Stuff that matters.

A comment on We now consider Moment.js to be a legacy project in maintenance mode. Parent comment

Re:We now consider Moment.js to be a legacy project in maint... by codegladiator on Tuesday September 15, 2020 @04:39AM (#24479100)
It "done" really, and I can use it today knowing its pros and cons. It would be "dead" if it had a glaring flaw which couldn't be fixed (which I don't think mutability is)

Every project has cons and they should embrace it and call it out like this project did instead of forever targeting a perfect library but nothing is perfect. It serves its purpose.

I am not sure if they are telling people not use it just because chrome now says to exclude it or they came up with it independently.

[ Parent | on HN ]
Re:We now consider Moment.js to be a legacy project in maint... by jayflux on Tuesday September 15, 2020 @04:58AM (#24479218)
> I am not sure if they are telling people not use it just because chrome now says to exclude it or they came up with it independently.

Independent. The maintainers have been recommending other alternatives (like Luxon) long before Chrome started to advise users on it. Moment has been in maintenance mode for a while now, this is just an updated confirmation of the fact, I'm guessing because users kept asking.

[ Parent | on HN ]
Re:We now consider Moment.js to be a legacy project in maint... by mj1586 on Tuesday September 15, 2020 @11:53AM (#24482684)
We (the Moment maintainers) have been saying it anecdotally for quite some time. In our respective podcasts, talks, Stack Overflow comments, etc. The Chrome thing simply encouraged us to make it an official position.
[ Parent | on HN ]