• @huginn
    link
    922 days ago

    It’d be nice to have that - yeah. My company issued me a laptop that only had 16gb of RAM to try and build Android projects.

    Idk if you know Gradle builds but a multi module project regularly consumes 20+GB of ram during a build. Despite the cost difference being paid for in productivity gains within a month it took 6 months and a lot of fighting to get a 32gb laptop.

    My builds immediately went from 8-15 minutes down to 1-4.

    • @CosmicTurtle0@lemmy.dbzer0.com
      link
      fedilink
      English
      -222 days ago

      I always felt that this is where cloud computing should be. If you’re not building all the time, then 32GB is overkill.

      I know most editing and rendering of TV shows happen on someone’s computer and not in the cloud but wouldn’t it be more efficient to push the work to the cloud where you can create instances with a ton of RAM?

      I have to believe this is a thing. If it isn’t, someone should take my idea and then give me a slice.

      • @huginn
        link
        322 days ago

        It’s how big orgs like Google do it, sure. Working there I had 192gb of ram on my cloudtop.

        That’s not exactly reducing the total spend on dev ram though - quite the opposite. It’s getting more ram than you can fit in a device available to the devs.

        But you can’t have it both ways: you can’t bitch and moan about “always on internet connections” and simultaneously push for an always on internet connected IDE to do your builds.

        I want to be able to work offline whenever I need to. That’s not possible if my resource starved terminal requires an Internet connection to run.

        Ram is dirt cheap and only getting cheaper.