[prmph]

Indeed, 8gb is plenty, even for serious work and coding, if you use the machine well.

If you think getting more and more RAM solves every performance problem, I've got news for you: People are having beachballs on machines with 32GB and more.

[garbageman]

I agree generally that on Mac you can 'get by' with 8gb and for the target audience on this, and how they'll likely use it - it's totally acceptable.

But if it's for serious work, this is not the device. 'Managing' the software to 'use the machine well' to get serious work done is unacceptable in 2026. It needs to just work and disappear into the background. I have enough to think about and micro managing the software running is out of the question.

[prmph]

> 'Managing' the software to 'use the machine well' to get serious work done is unacceptable in 2026

I agree, I just don't think the rush to get more and more RAM and storage is the root of the problem.

Why on earth does a browser need more than 10 GB to display web pages?? Why does macOS keep piling/hiding trash that should be deleted in "System Data"?

And, if you need to keep device backups, put them on an external drive; that's what those things are for.

[astrange]

Web pages are very complicated and there's no pressure on people to make less complicated ones, nor is there any way there could be pressure on them.

Images, complicated CSS, JavaScript ads, they can all use lots of memory!

[carlosjobim]

It depends on how you define "serious work". Is it to get the best results possible, or is it to tax a computer as much as possible? Programmers would usually answer the latter, while users would answer the former.

That's why programmers put their stuff into Kubernetes which go into virtual machines, which go into eleven layers of javascript abstraction which go into twelve thousand node packages, which go into something else to end up with something with very basic functionality, which usually doesn't work very well.

Other pro computer users are focused on the results, so they use professional office software, calendars, communications, photo and video editing and effects, photo-realistic 3D editors, studio level audio and music editing software. All which lives perfectly fine on 8GB of RAM.

[vunderba]

As always - it depends on the kind of ostensible "serious work" you do.

I've got 32GB and often work with legacy .NET Winform/WPF applications on a Macbook. That means spinning up a Windows 11 ARM distro virtual machine and running Microsoft Visual Studio. The VM has 8GB of ram allocated to it, and based on qemu-system memory pressure, it hovers around ~4-6GB of that.

I also do a lot of colorgrading and video editing with longform 4K videos using Davinci Resolve - scrubbing in an uncompressed format would absolutely thrash the hell out of your swap with only 8GB.

[AlotOfReading]

Add much as I'd like to be more efficient, modern toolchains absolutely need these kinds of numbers for big projects. My 48GB system will OOM trying to link clang unless I'm extremely careful. The 64GB system is a bit more forgiving, but I still have to go for lunch while it's working.

Sure, might be ambitious to do that sort of workload on a budget conscious laptop, but it'd be nice y'know?

[jshen]

If you're trying to link clang, this laptop is not for you. It's for people that would consider a chromebook for their use case.

[prmph]

Usually the problem then is more fundamental.

Rust exists. If you insist on using (or need to use) languages with horrendous build architectures like C++, then you probably need a proper build server then anyways.

I don't have XCode on my Macbook and have resolved not to do iOS development any time soon (although ideally I'd have wanted to dabble in it sometimes), because I've accepted I don't want to run the rat race of always needing beefier and beefier machines to keep up with Apple's bad habit of bloating it up for each version up for no good reason.

I don't run local LLMs on my machine, since even with 100s of GB of RAM, I hear the performance you can expect is abysmal.

I think it is a good idea to put pressure on hardware and software vendors to make their products more efficient.

[AlotOfReading]

Rust has similar issues with memory usage during linking as C++.

I can use a build server when I want one, but that's not always appropriate. Local builds are useful.

[restes]

>People are having beachballs on machines with 32GB and more.

Well, sure, because the beachball means the main thread is hung, and that can happen for many reasons unrelated to memory pressure.