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

    • haui
      link
      fedilink
      English
      541 month ago

      Exactly. Same here. The fact that „linux“ isnt a product that has to have the shiny new thing after every update and has no deadlines to hold and no manager to keep happy makes it a fundamentally different thing which actually is very much in line with efficiency ideas, the idea of progress and evolution as a whole. At least thats how I view it.

      • @not_woody_shaw
        link
        English
        231 month ago

        The shiny new thing can be better code to do the same thing.

  • @[email protected]
    link
    fedilink
    English
    72
    edit-2
    1 month ago

    Back in the day there was a Mac OS update (Snow Leopard) that took gigabytes off. They dropped support for PowerPC CPUs. So the compiled binaries basically got slashed in half.

    The goals of Snow Leopard were improved performance, greater efficiency and the reduction of its overall memory footprint, unlike previous versions of Mac OS X which focused more on new features. Apple famously marketed Snow Leopard as having “zero new features”.[13] Its name signified its goal to be a refinement of the previous OS X version, Leopard.

    https://en.m.wikipedia.org/wiki/Mac_OS_X_Snow_Leopard

        • @[email protected]
          link
          fedilink
          English
          141 month ago

          Well they haven’t made a single x86 machine in what, 4 or 5 years?

          The 2024 version of MacOS doesn’t support anything older than 2017 and for most models it’s more like 2018-2020

          I’d say in 2-3 years they’ll drop support for all x86 machines, at which point first party binaries can stop shipping with x86 code. Then eventually, several years later, they’ll drop support for x86 emulation via Rosetta 2, so that’s another thing they can drop from the OS. And once xcode stops giving you those fat dual-arch binaries, other software will also take a bit less space.

          • Estebiu
            link
            fedilink
            English
            129 days ago

            Oh i though you were talking about discontinuing x86 in general, even for non-apple devices. Yeah I agree, x86 macbook have maybe another 4-5 years max

        • irelephant 🍭
          link
          fedilink
          English
          61 month ago

          idk, apple is very trigger-happy when it comes to discontinuing things (outside of the iphones, strangely.) i think by 2030 we will be long gone from apple x86 machines.

    • @Duamerthrax
      link
      English
      151 month ago

      God, Snow Leopard was peak Apple.

      • @Cenzorrll
        link
        English
        61 month ago

        As an avid apple disliker, they really got a lot of things right with 10.x, with snow leopard hitting it out of the park. Everything from them around that era was slick. If I wasn’t a poor college kid running a 5 year old eBay Thinkpad I would have been sucked into their oppressive ecosystem in a heartbeat.

        • @Duamerthrax
          link
          English
          11 month ago

          There’s a different timeline where the board also brought back Wozniak, OS X has linux under the hood and all third party software was cross compatible.

          I wouldn’t imagine iTunes on Ubuntu, but think if all that annoying office software that keeps workplace from switching to linux was suddenly available?

      • @[email protected]
        link
        fedilink
        English
        221 month ago

        Yes. Thats how they made everything seem magical to the end user.

        Two architectures, and two binaries in the single package.

        All those programs that only had binaries in the old architecture ran through the emulator Rosetta.

        Once the old architecture had been deprecated long enough, they dropped the PPC compilation in the binaries.

        There was the technique to regain disk space by deleting the unused architecture binaries from the bundles.

      • @[email protected]
        link
        fedilink
        English
        71 month ago

        I don’t know if that’s what they did for the PowerPC -> Intel switch, but now with the Intel -> ARM switch, Xcode compiler tools spit out dual arch binaries, so you can run the same binary natively on x86 or ARM. Things that aren’t compiled that way yet and only have x86 binaries, will be run using Rosetta 2.

        Doesn’t matter much to the end user though. It’s all just pretty seamless if you’re on an ARM Mac and idk if there’s much or any problems on x86 Macs yet regarding binary compatibility. I actually doubt there is.

      • @[email protected]
        link
        fedilink
        English
        31 month ago

        That OS was the last of Apple to come on optical media. So, no pushing. Buying physically.

      • @[email protected]
        link
        fedilink
        English
        11 month ago

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

        • Captain Aggravated
          link
          fedilink
          English
          31 month 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.

          • @[email protected]
            link
            fedilink
            English
            4
            edit-2
            1 month 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!

              • Cousin Mose
                link
                fedilink
                English
                127 days ago

                I think this is available on Linux too if I remember correctly. You can compile a binary that contains multiple architectures. It’s been awhile but I think ELF binaries can do it.

  • @Rooty
    link
    English
    59
    edit-2
    1 month ago

    OS is bloat, if you’re not shifting CPU registers by hand are you even a Linux user?

    spoiler

    No, because Linux is a kernel/OS, and OS is bloat

    • @sir_pronoun
      link
      English
      261 month ago

      Exactly, you boot the kernel, then get out the electron microscope to twiddle those bits (which is why Linux users are perverts)

    • @Hiro8811
      link
      English
      12
      edit-2
      1 month ago

      paccache -r

      There done

      • swab148
        link
        fedilink
        English
        41 month ago

        I just got the hook from the AUR, don’t even have to think about it lol

  • @[email protected]
    link
    fedilink
    English
    231 month ago

    I’m not a programmer by any means, but I’m guessing, they are just removing old redundant features and code, but I could be very wrong here.

    • lime!
      link
      fedilink
      English
      241 month ago

      a new version of a program can also move to a different set of dependencies that is shared with another program, so you don’t need to keep both around.

      • @patatahooligan
        link
        English
        131 month ago

        This wouldn’t appear like this when upgrading the system with pacman. pacman does not automatically remove orphaned dependencies during upgrades. You have to query for them and remove them explicitly as a separate operation afterwards. So in the OP what we’re seeing is the new versions of packages themselves getting smaller.

          • swab148
            link
            fedilink
            English
            41 month ago

            Good ol’ pacman -Rns $(pacman -Qqtd), or as I’ve aliased it, orphankiller

            • lime!
              link
              fedilink
              English
              21 month ago

              saved me a gig ^^

              had some old plasma5 stuff lying around from before the upgrade.

    • LungOP
      link
      English
      1
      edit-2
      1 month ago

      I remember one internship in college, I realized that after 4 months of work, the result was 15k lines less code than when I started. I figured out new ways to structure the system so it was much easier to write and maintain, while actually adding features. That felt great

      And yeah, there are many ways for it to happen. Ex. someone was shipping the tests with the code and decided to stop, debug symbols being removed, inlined dependencies being externalized, maybe a new version of a UI toolkit has extra icons built in

      Efficiency can gently creep in. What blows my mind is that this is averaged out across so many packages at once. And sure, sometimes it goes up too, but nothing like Windows/OSX. It’s really cool that you can make a Linux that will fit into ~any space you want, whereas the min requirements for Win11 include 64gb of hd

  • @postmateDumbass
    link
    English
    181 month ago

    So tired of android eating my carefully set aside free space.

  • @[email protected]
    link
    fedilink
    English
    181 month ago

    Decided to try this out on Tumbleweed. I last updated yesterday. Today I have 4 packages to upgrade and doing so will drop ruby 3.3. Looks like I also have Ruby 3.4 installed so likely I had a package depending on 3.3 and another on 3.4 and now the 3.3 has moved to 3.4. I regained a whopping 30 MB disk space!

  • @okamiueru
    link
    English
    131 month ago

    Thanks for the reminder to update

  • slazer2au
    link
    English
    111 month ago

    I keep forgetting to run apt autoremove to save even more space.

  • @AnUnusualRelic
    link
    English
    61 month ago

    Wow I’ve never had an update with so few packages.

    • LungOP
      link
      English
      51 month ago

      Out of all the comments here hahaha this is the one that gets me lmao

      You haven’t had an update with less than 52 packages?? Ever??