Comment on

Shanmugha@lemmy.world ⁨3⁩ ⁨days⁩ ago

• lime@feddit.nu ⁨3⁩ ⁨days⁩ ago

  ever heard of node.js?

  source

  • Shanmugha@lemmy.world ⁨3⁩ ⁨days⁩ ago

    Heard, not used though. isEven™ too, but I never thought it goes like this in anything intended for external use

    source

    • lime@feddit.nu ⁨3⁩ ⁨days⁩ ago

      there’s at least one guy i know of on github whose claim to fame is he finds code in existing codebases by big corpos that’s duplicated, breaks it out into a library, then PRs the original codebase with “instead of doing <this part> manually, switch to depending on this library”, then adds to his profile “my code is used by <big corpo>”. he had thousands of libraries like that last i checked, most of them less than ten lines of code.

      source

      • Shanmugha@lemmy.world ⁨3⁩ ⁨days⁩ ago

        Damn. isEven come alive. But hilarious enough to watch someone do it :)

        source
    • jayands@lemmy.world ⁨3⁩ ⁨days⁩ ago

      Your node_modules directory can get so bloated that the community came up with different package managers just for deduplication! pnpm, for example, makes one global-adjacent cache, and then just symlinks the dependencies as needed. This is because the regular npm doesn’t, because what if the package changed between the 20ms since I downloaded it for nuxt? (Sorry Nuxt users, had to pick a name)

      source

      • Shanmugha@lemmy.world ⁨3⁩ ⁨days⁩ ago

        Given an example from another reply… yeah. Things are fucked

        source
• ICastFist@programming.dev ⁨3⁩ ⁨days⁩ ago

  There’s a term called “dependency hell”. Sure, this one dependency is fine, but it depends on 3 other libraries, those 3 depend on a sum of 7 others, etc…

  xkcd.com/1579/

  source

  • Shanmugha@lemmy.world ⁨2⁩ ⁨days⁩ ago

    Nah, dependency hell is when two things you want to use depend on same thing, but different versions. The depth of dependencies needed to make “this one thing” work may or may not be a problem

    source
  • corsicanguppy@lemmy.ca ⁨3⁩ ⁨days⁩ ago

    It’s exacerbated by “oh this library is updated for no reason than its version is newer so we need to force that bleeding edge on any ecosystem we’re in” thinking.

    We’ve absolutely lost the careful, measured long-term release and maintenance cadence that we built the Internet on.

    Compare Systemd.

    source

    • 3abas@lemmy.world ⁨3⁩ ⁨days⁩ ago

      The worst dependency hell is when a library has a strict version dependency, and another library uses that same dependency. When the second library updates their minimum version of the dependency to one that is higher than the exact version needed for the first, THAT’S dependency hell.

      source

      • phlegmy@sh.itjust.works ⁨2⁩ ⁨days⁩ ago

        This wouldn’t be a problem if libraries didn’t frequently make breaking changes to their api.

        “Move fast and break things” is for startups with no userbase, not libraries with millions of users.

        source

        • -> View More Comments