There were a number of exciting announcements from Apple at WWDC 2024, from macOS Sequoia to Apple Intelligence. However, a subtle addition to Xcode 16 — the development environment for Apple platforms, like iOS and macOS — is a feature called Predictive Code Completion. Unfortunately, if you bought into Apple’s claim that 8GB of unified memory was enough for base-model Apple silicon Macs, you won’t be able to use it. There’s a memory requirement for Predictive Code Completion in Xcode 16, and it’s the closest thing we’ll get from Apple to an admission that 8GB of memory isn’t really enough for a new Mac in 2024.

  • maxinstuff@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    5 months ago

    Oh man, I remember so many people defended 8GB since the M1 first came out (and since).

    I always argued it would significantly reduce the lifetimes of these machines if you bought one, not just because you’d be swapping a lot more on the (soldered in BTW) ssd, but because after a few years of updates it would become unbearably slow, or hardware would fail, or both.

    Didn’t stop people constantly “tHe aRchITecTuRE iS cOmPlETelY diFFeRenT!!!”

    Sure it’s different, but it’s still just a computer. A technical person can still look at the spec sheet and calculate effective performance accounting for bus widths etc.

    Disclosure: I bought a top spec 16GB M1 Mac Air on launch and have been extremely happy with it - it’s still going strong.

    • uis@lemm.ee
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      5 months ago

      Didn’t stop people constantly “tHe aRchITecTuRE iS cOmPlETelY diFFeRenT!!!”

      Different Turing Machine on different math and alternative physics, I guess.

      I bought a top spec 16GB M1 Mac Air on launch

      My condolences.

      EDIT: do people geuenly belive that math doesn’t apply to Apple’s products or they just don’t understand even such concentrated sarcasm?

  • kingthrillgore@lemmy.ml
    link
    fedilink
    English
    arrow-up
    0
    ·
    5 months ago

    They moved to on-die RAM for a reason: To nickel and dime yo ass.

    I needed to expense a Mac Mini for iOS development, and everyone (Me, the company, our purchasing department) was baffled at how much it cost to get 16 GB. And they only go up to 24GB. Imagine how much they’ll charge for 32 in a year!

      • Echo Dot@feddit.uk
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        5 months ago

        It’s a bit first but if their primary motivation was performance improvements they wouldn’t be soldering 16 GB.

        If you’re going to weld shoes to your feet, you better at least make sure that they’re good shoes.

          • Echo Dot@feddit.uk
            link
            fedilink
            English
            arrow-up
            0
            ·
            edit-2
            5 months ago

            Yeah but if you’re only putting 8 GB of RAM on then you’re also going to be constantly querying the hard drive. So any performance gain you get from soldering, is lost by going all the way to the hard drive every 3 microseconds.

            It’s only better performance on paper in reality there’s no real benefit. If you can run an application entirely entirely within the 8 GB of RAM, and assuming you’re not running anything else, then maybe you get better performance.

            • sugar_in_your_tea@sh.itjust.works
              link
              fedilink
              English
              arrow-up
              0
              ·
              5 months ago

              And that’s the idea. Soldering memory is an engineering decision. How much to solder is a marketing decision. Since users can’t easily add more, marketing can upsell on more RAM.

              It’s not “on paper,” the RAM itself is performing better vs socketed RAM. Whether the system runs better depends on the configuration, as in, did you order enough RAM.

              • Echo Dot@feddit.uk
                link
                fedilink
                English
                arrow-up
                0
                ·
                5 months ago

                I can’t tell if you’re a stooge or if you really think that. I hope you are stooge, because otherwise that’s a really stupid position you’ve decided to take and you clearly don’t actually understand the issue.

  • Hux@lemmy.ml
    link
    fedilink
    English
    arrow-up
    0
    ·
    5 months ago

    This isn’t a big deal.

    If you’re developing in Xcode, you did not buy an 8GB Mac in the last 10-years.

    If you are just using your Mac for Facebook and email, I don’t think you know what RAM is.

    If you know what RAM is, and you bought an 8GB Mac in the last 10-years, then you are likely self-aware of your limited demands and/or made an informed compromise.

  • seb@programming.dev
    link
    fedilink
    English
    arrow-up
    0
    ·
    5 months ago

    I have a macbook air m2 with 8gb of ram and I can even run ollama, never had ram problems, I don’t get all the hate

    • sverit@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      5 months ago

      Which model with how many parameters du you use in ollama? With 8GB you should only be able to use the smallest models, which ist faaaar from ideal:

      You should have at least 8 GB of RAM available to run the 7B models, 16 GB to run the 13B models, and 32 GB to run the 33B models.

  • Jtee@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    5 months ago

    And now all the fan boys and girls will go out and buy another MacBook. That’s planned obsolescence for ya

    • Mongostein@lemmy.ca
      link
      fedilink
      English
      arrow-up
      0
      ·
      5 months ago

      And the apple haters will keep making this exact same comment on every post using their 3rd laptop in ten years while I’m still using my 2014 MacBook daily with no issues.

      Be more original.

      • Jtee@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        5 months ago

        Nice attempt to justify planned obsolescence. To think apple hasn’t done this time and time again, you’d have to be a fool

        • Mongostein@lemmy.ca
          link
          fedilink
          English
          arrow-up
          0
          ·
          edit-2
          5 months ago

          👍

          -posted from my ten year old MacBook which shows no need for replacement

          • Honytawk@lemmy.zip
            link
            fedilink
            English
            arrow-up
            0
            ·
            5 months ago

            At which point did Apple decide your MacBook was too old to be usable and stop giving updates or allow new software to run on it?

            • Mongostein@lemmy.ca
              link
              fedilink
              English
              arrow-up
              0
              ·
              edit-2
              5 months ago

              Still gets security updates. All the software I need to run on it runs on it.

              My email, desktop, and calendar all still sync with my newer desktop. I can still play StarCraft. I can join zoom meetings while running Roll 20. I can even run Premiere and do video editing… to a point.

              I guess if you need the latest and greatest then you might have a point, but I don’t.

              This whole thread is bitching about software bloat and Apple does that to stop the software bloat on older machines, but noooo that’s planned obsolescence. 🙄

    • bamboo@lemm.ee
      link
      fedilink
      English
      arrow-up
      0
      ·
      5 months ago

      Someone who is buying a MacBook with the minimum specs probably isn’t the same person that’s going to run out and buy another one to get one specific feature in Xcode. Not trying to defend Apple here, but if you were a developer who would care about this, you probably would have paid for the upgrade when you bought it in the first place (or couldn’t afford it then or now).

  • _number8_@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    5 months ago

    imagine showing this post to someone in 1995

    shit has gotten too bloated these days. i mean even in my head 8GB still sounds like ‘a lot’ of RAM and 16GB feels extravagant

    • rottingleaf@lemmy.zip
      link
      fedilink
      English
      arrow-up
      0
      ·
      5 months ago

      I still can’t fully accept that 1GB is not normal, 2GB is not very good, and 4GB is not all you ever gonna need.

      If only it got bloated for some good reasons.

      • Honytawk@lemmy.zip
        link
        fedilink
        English
        arrow-up
        0
        ·
        5 months ago

        The moment you use a file that is bigger than 1GB, that computer will explode.

        Some of us do more than just browse Lemmy.

        • rottingleaf@lemmy.zip
          link
          fedilink
          English
          arrow-up
          0
          ·
          5 months ago

          Wow. Have you ever considered how people were working with files bigger than total RAM they had in the normal days of computing?

          So in your opinion if you have 2GB+ of a log file, editing it you should have 2GB RAM occupied?

          I just have no words, the ignorance.

      • Aux@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        5 months ago

        High quality content is the reason. Sit in a terminal and your memory usage will be low.

        • lastweakness@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          5 months ago

          So we’re just going to ignore stuff like Electron, unoptimized assets, etc… Basically every other known problem… Yeah let’s just ignore all that

          • Aux@lemmy.world
            link
            fedilink
            English
            arrow-up
            0
            ·
            5 months ago

            Is Electron that bad? Really? I have Slack open right now with two servers and it takes around 350MB of RAM. Not that bad, considering that every other colleague thinks that posting dumb shit GIFs into work chats is cool. That’s definitely nowhere close to Firefox, Chrome and WebStorm eating multiple gigs each.

            • lastweakness@lemmy.world
              link
              fedilink
              English
              arrow-up
              0
              ·
              5 months ago

              Yes, it really is that bad. 350 MBs of RAM for something that could otherwise have taken less than 100? That isn’t bad to you? And also, it’s not just RAM. It’s every resource, including CPU, which is especially bad with Electron.

              I don’t really mind Electron myself because I have enough resources. But pretending the lack of optimization isn’t a real problem is just not right.

              • Aux@lemmy.world
                link
                fedilink
                English
                arrow-up
                0
                ·
                5 months ago

                First of all, 350MB is a drop in a bucket. But what’s more important is performance, because it affects things like power consumption, carbon emissions, etc. I’d rather see Slack “eating” one gig of RAM and running smoothly on a single E core below boost clocks with pretty much zero CPU use. That’s the whole point of having fast memory - so you can cache and pre-render as much as possible and leave it rest statically in memory.