Not entirely the usual fare, but i figured some here would appreciate it

I often rag on the js/node/npm ecosystem for being utter garbage, and this post is a quite a full demonstration of many of the shortcomings and outright total design failures present in that space

  • V0ldek@awful.systems
    link
    fedilink
    English
    arrow-up
    3
    ·
    9 months ago

    Okay, I might be brainfarting here, but… why is blocking _un_publishing such a big deal? I understand that it might be annoying, but this talks about it like it broke the fucking system, as if it was as important as actually publishing packages.

    How often do people in JS world unpublish packages?

    • froztbyte@awful.systemsOP
      link
      fedilink
      English
      arrow-up
      5
      ·
      9 months ago

      seems like a perfectly normal thing to do to me. maybe you uploaded it under the wrong account, or licensing change, or need to do a security- or danger-related retraction, or …

      hell, maybe you just changed your mind! that’s allowed too! or should be

      • V0ldek@awful.systems
        link
        fedilink
        English
        arrow-up
        4
        ·
        9 months ago

        I totally get that it’s a normal thing and it is a disruption of service, but it doesn’t strike me as “everybody freak out”.

        If, say, Lemmy stopped you from deleting your comments for 24h few would even notice.

        • earthquake@lemm.ee
          link
          fedilink
          English
          arrow-up
          6
          ·
          edit-2
          9 months ago

          I am guessing* that the “everybody freak out” part happened when the extent became evident and everyone realized all of npm was suddenly unpublishable, not so much because everyone individually freaked out individually immediately.

          *extrapolating from the NPM community being described as frustrated but mostly forgiving.