Love to see upgrades with a negative net size lmao. Software should get more optimized with time, not more bloated. Oop, just got the gnome console popup notification saying that my install command finished running, sweet – it took as long as making this post

  • rhombus@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    ·
    12 hours ago

    It probably made the downloaded binary smaller, but the actual instal size for x86 machines probably didn’t change much.

    • Captain Aggravated@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      11 hours ago

      …what?

      We’re talking about the end of the transitional period from PowerPC (the G3 and G4 iMacs and iBooks) to the Intel architecture (about the time they went to the Macbook nomenclature). If I read this right, they didn’t push separate PowerPC and Intel architecture versions, you’d just get MacOS (or in those days, OSX) and it would ship with both binaries. Which, compiled binaries would be quite different for different architectures, data files, graphics, interpreted code etc. would be similar but pre-compiled binaries would be different.

      I know for awhile a lot of applications were only available for PowerPC, so they did the Rosetta translation layer, which is a reason why you’d find PowerPC binaries on an Intel system. They did exactly that again with the transition from x86 to ARM.

      • boonhet@lemm.ee
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        9 hours ago

        I already responded to you in another comment, but:

        If I read this right, they didn’t push separate PowerPC and Intel architecture versions, you’d just get MacOS (or in those days, OSX) and it would ship with both binaries.

        No, it’s even crazier than that. You didn’t get separate PowerPC and Intel binaries either. You got fat binaries that had machine code for both architectures!