35
Comments
  • 17
    Backwards compatibility? Forward compatibility?
  • 6
    @gronostaj as far as I know it’s not directly exposed in their api but only being used internally, however you’re right it’s probably a placeholder for future implementation.

    Still funny tho. I would add a TODO or something at least
  • 6
    Reminds me of mootools aliasing functions because they misspelled their names.
    But it was released so long ago, they couldn't just rename it.
  • 12
    @gronostaj Sideways compatibility?
  • 2
    @PonySlaystation Like, with parallel branch? ;)
  • 5
    JS devs being JS devs.

    I'm starting to think this is miles ahead of the league these days.

    https://www.npmjs.com/package/lpad
  • 3
    I talked about moment.js with a colleague the other day. It's causing a lot of performance issues in our codebase. Considering swapping it out for day.js, or even just plain old Date
  • 3
    Ah yes, string oof = preParseFormat(oof);
  • 1
    @ScriptCoded We’re having same issues and I’m doing this exactly atm. I’m trying to replace it with good old native Date.
  • 1
    Wait a minute
  • 0
    FUCKINNNNGG HA! AND THAT PIECE OF SHIT IS HUUUUGE. For what???? For parsing time??????? Fucking hilarious.

    What a fucking piece of shit library this is.

    Thank you for demonstrating it. Idiot devs like these ruin the js ecosystem.
  • 3
    @ScriptCoded Can recommend, switched to date-fns myself
  • 0
    I also saw some of those alternatives, but then again Angular Material supports moment 🙄
  • 0
    I can’t stand material as a design or angular as a framework so those two words together give me instant anxiety 😅😂
  • 0
    @FastFwd00 mind elaborate? I find angular pretty good, consistent and not big learning curve.
  • 0
    @WorstVarNames not really. It’s just my subjective opinion. I prefer React and I think material looks ugly
  • 0
    Prob a placeholder?
  • 0
    Identity function right there!
Add Comment