You can play it in your browser here.

  • frezik@midwest.social
    link
    fedilink
    English
    arrow-up
    0
    arrow-down
    2
    ·
    edit-2
    9 months ago

    And there’s almost always a reason. Code size tends to be modest compared to supporting data around it.

    • I Cast Fist@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      ·
      9 months ago

      I see you’ve never dealt with a real life project that requires god knows how many different libraries off nodejs because 🤷‍♂️

      Dependency hell takes a lot of space.

      • frezik@midwest.social
        link
        fedilink
        English
        arrow-up
        0
        arrow-down
        1
        ·
        edit-2
        9 months ago

        I have. Still small compared to the images and such that are used in a user facing application.

        Edit: just to bring in real numbers, I have an old TypeScript project that results in a 109M node_modules dir. Which I agree is absurd. I also have an old anime video, 21 minutes long, at only 560x432 resolution, 24fps, which takes 171M. And that’s my point: even in really bad cases, code size tends to be swamped out by everything else in user-facing applications. If there’s any kind of images, music, or video, the code size will be a small part of the complete picture.