I think some raised points are relevant…

  • kornel@lemmyrs.org
    link
    fedilink
    English
    arrow-up
    14
    ·
    1 year ago

    I maintain a long-term Rust + Node.js project, and the Node side is the painful one.

    Node makes backwards-incompatible changes, and doesn’t have anything like the editions to keep old packages working. I can end up with some dependencies working only up to Node vX, and some other deps needing at least Node v(X+1).

    • AggressivelyPassive@feddit.de
      link
      fedilink
      arrow-up
      6
      ·
      1 year ago

      That’s an issue with almost the entire js ecosystem. I’m part of a project that has rather high security standards, so we have to keep everything updated. The Java side is almost trivial, update some version number, let the tests run and you’re fine. The js side is a constant battle against incompatibilities, weird changes for no reason and simply tons of vulnerabilities.