Re:We now consider Moment.js to be a legacy project in maint...
by mvc on Tuesday September 15, 2020 @06:14AM
(#24479607)
Usually when bringing in a library dependency, you don't use all features from the library. If the updates to some library relate to things you don't use, and the rest remains compatible, then why update?
[ Parent
| on HN ]
Re:We now consider Moment.js to be a legacy project in maint...
by mschuster91 on Tuesday September 15, 2020 @06:26AM
(#24479655)
Because not every language / environment allows concurrent versions of a single library. PHP definitely does not, and for Java stuff IIRC you can only have one version of a library in one context of Tomcat/whatever application server you use.
Therefore you want to keep your code at least somewhat up to date so that people don't run into weird bugs.
Re:We now consider Moment.js to be a legacy project in maint...
by scoopertrooper on Tuesday September 15, 2020 @06:47AM
(#24479754)
Security teams generally have policies that require dependencies be up-to-date within a certain time frame. This is especially true if the dependency has a CVE somewhere within it - even if that CVE affects functionality that isn't utilised by the project.