Live data from Hacker News

We now consider Moment.js to be a legacy project in maintenance mode

momentjs.com

1–10 of 266 posts

Re: We now consider Moment.js to be a legacy project in maintenance mode

#3
Pretty reasonable stance, all in all. Modern practices have changed, and favoring not breaking huge chunks of the existing web chasing new usages (that may already be accomplished well by other libraries) is a reasonable and professional stance.

Re: We now consider Moment.js to be a legacy project in maintenance mode

#5
Good for them. Open Source seems to have an irrational fear of done.

Done is good. Done should be the goal.

But it’s not. Because if you’re not adding new features and pushing code changes every day, your project is abandoned, dead. To quote another thread from two minutes ago: “I’m quite sad to see the end of Moment.js”

I wish the was a way to fix this attitude. So that project maintainers didn’t need to write two page apologies for finishing their thing.

Re: We now consider Moment.js to be a legacy project in maintenance mode

#6
post #2

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

Honestly, I wish more js libraries would be that way. I’ve used date-fns in a small part of an app, so of course when I return to it in several months, date-fns released a fully incompatible new major version.

Re: We now consider Moment.js to be a legacy project in maintenance mode

#9
It's been common knowledge in the front end development community for quite a while now to avoid Moment.js due to it's file size. Glad to see the maintainers agree. I'm thankful for the work they did in progressing date/time management libraries as a whole, but just like jQuery there's now better alternatives.
Post reply on HN