We now consider Moment.js to be a legacy project in maintenance mode (momentjs.com)

Article summary

The Moment.js project is now considered a legacy project in maintenance mode, with its maintainers discouraging its use in new projects. The project will still receive updates for security and compatibility, but no new features will be added. Moment-Timezone will continue to be updated to follow IANA time zone database releases. The decision is due to the project's design and technical limitations, which make it less suitable for modern JavaScript development.

Main themes

• Legacy project maintenance
• JavaScript development best practices
• Technical debt and limitations
• Immutability and convention
• Ecosystem stability and versioning
• Library choice and brand value

What commenters say

• Some commenters appreciate the maintainers' decision to declare the project done and focus on stability, rather than constantly adding new features.
• Others disagree, citing the project's reliability and ease of use, and arguing that it should continue to be developed and improved.
• The project's technical limitations, such as mutable objects and large bundle size, are seen as major drawbacks by some, while others argue that these issues can be worked around.
• There is a debate about the importance of immutability in JavaScript, with some arguing that it is a fundamental flaw in the language, while others see it as a minor issue that can be addressed through convention and best practices.
• Some commenters note that the JavaScript ecosystem is prone to breaking changes and version conflicts, making it difficult to maintain long-term stability.
• The decision to discourage the use of Moment.js in new projects is seen as a reasonable one by some, given the project's limitations and the availability of alternative libraries.
• Others argue that the project's brand value and reputation for reliability make it a trustworthy choice, despite its technical limitations.