They seem to be too big for what devs claim to be a ‘minor patch’ and yet too small to suggest a complete reinstallation of the app. Is there some technical reason behind it? I would like to request an ELI5 for this.

  • zirzedolta@lemm.eeOP
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    Lol I thought at first devs calculated exactly what portions of the apps need updating and uploaded only that much portion in the app stores. I dunno what to make of this discovery now.

    • Darkassassin07@lemmy.ca
      link
      fedilink
      English
      arrow-up
      14
      arrow-down
      1
      ·
      1 year ago

      That can get really convoluted, especially when users update at different times from different past versions.

      One user may be able to make the most recent changes as they have the most recent version not including the update thats being pushed right now; another user however may be 15 revisions behind and have to find and apply each of those 15 updates in the correct order to arrive at the same set of files.

      It’s much easier to just push the most recent set of files in their entirety to users and have them replace whatever they’ve got. Then you know they didn’t make any mistakes applying several subsequent changes in a row.

    • wildbus8979@sh.itjust.works
      link
      fedilink
      arrow-up
      7
      ·
      1 year ago

      That’s fairly easy to do for interpreted languages, but it’s a lot more problematic for compiled apps that are distributed as a machine code binary.

    • noddy@beehaw.org
      link
      fedilink
      arrow-up
      5
      ·
      1 year ago

      I think windows update does that, or at least used to do. That’s why it is so slow to update, because you need every update in succession, you can’t just grab the latest one.