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

Post by mj1586 » Tue, Sep 15, 2020, 4:10 PM UTC

cjkarr wrote: post #168

I don't know if the Moment.js folks are reading this, but THANK YOU for your commitment to stability and security fixes. Not all of us are in a situation where we're iterating through the JavaScript new hotness every couple years and still have significant legacy systems to maintain and support.

Post by winstonewert » Tue, Sep 15, 2020, 4:40 PM UTC

throwaway189262 wrote: post #38

kqr wrote: post #27

Earlier quoted context omitted.

> Until very recently it was impossible to make objects immutable in JS. Even now its really only done using third party libraries. There's a big difference between "literally impossible to mutate" (only important in the most security-critical contexts) and "designed around immutability as the default" (which is what is desired in most of the real world.) The former not being possible is not a reason to exclude the l…

With JS, until recently, it was nearly impossible to design immutable API's. Everything takes JSON based objects which have no field accessors. All the objects underneath are just hashmaps with string keys. When all your objects are hashmaps you can't really make fields immutable. Even if you wrote getters, someone can just reassign the function reference. Even if you check your fields in incoming object parameters,…

Post by kevmo » Tue, Sep 15, 2020, 4:54 PM UTC

qwertox wrote: post #82

A big "Thank you!" to the developers of Moment.js. For the last 8 years or so it has always been the first library I included in any new JS-project. I didn't even bother looking for alternatives, so I didn't know about Intl, Luxon & day.js until today. The size of the library has always been one of these things where I thought that the benefits outweigh the costs, and I knew that it wouldn't be like this forever. To…

     No other library has filled a huge gap in JavaScript like Moment.js did for so many years.

Post by riquito » Tue, Sep 15, 2020, 4:59 PM UTC

jeroenhd wrote: post #158

dmit wrote: post #52

Please pardon this drive-by assessment of JS calendar libraries by a casual user. moment.js: Mutable. Thank you, next. Luxon: Takes the effort to implement `Interval`, which would be `Range ` in any proper language, but somehow avoids providing separate `Date` and `Time` objects. Day.js: When you kinda like moment.js, but your bundler says it's too fat. date-fns: The finest of pure, curry-able functions over the mine…

Can you explain why you find mutability to be a showstopper? Is this a front end developer thing? I like my consts and all where relevant, but I don't see why mutability is such a problem. Javascript is an imperative language where almost everything more complicated than a number is mutable. I see the lack of creating copies of objects with every operation as a benefit because of the RAM and CPU cycles it saves. Is i…

Post by firebaze » Tue, Sep 15, 2020, 5:14 PM UTC

  const somedate = moment(...somedate...);
  const oneMonthLater = somedate.add(1, 'M');
  const dateToCheck = ...; // between somedate and somedate + 1 month

  if (dateToCheck.isBetween(somedate, oneMonthLater)) {
    // do something
  }