You can play it in your browser here.

  • @[email protected]
    link
    fedilink
    English
    10
    edit-2
    27 days ago

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

    • I Cast Fist
      link
      fedilink
      English
      1127 days 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.

      • @[email protected]
        link
        fedilink
        English
        7
        edit-2
        27 days 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.

        • I Cast Fist
          link
          fedilink
          English
          327 days ago

          As a point of comparison, in the last place I worked, the main project had over 600MB of javascript dependencies it pulled from node. Plus 300MB of python libraries for Django and whatever else.

          At my current job, preparing your environment for development of one “isolated” php system will need at least 3GB of dependencies. Even the main programmer behind it has no clue how it happened or why.