[foldr]

>The probability that a person buying a n 8Gb pro will find it limited is very high.

Perhaps, but I would like to see evidence for this based on actual tests. Most of the commentary here just takes it as axiomatic that 8GB won't be enough and isn't based on actual comparisons of the 8GB and 16GB models.

[figassis]

My employer provided 8GB mbp has a hard time running some nodejs container workloads. The build step is particularly resource intensive to the point it slows down the whole system. So if you're developing with auto reload enabled, you're in for a hard time. So my solution is to use a separate intel server I have around, with VS Code remote extension. So now I'm tied to that server and my MBP is reduced to being an expensive terminal. If I travel, I can't work without a stable connection to that server. But that was exactly why MBP exists, to allow professionals to do their work. Had I not had the server, that'd be impossible.

[foldr]

Ok, it’s definitely believable that container workloads would be difficult in 8GB, but have you ever tried the same workload on a 16GB model?

I obviously don’t have stats on this, but I suspect it’s a tiny minority of base model MacBook Pros that ever run a container.

[figassis]

Seems like you’re putting a lot of effort in stretching the definition of pro to defend Apple. I have a personal 16GB mbp, they both struggle. Still don’t see your point.

[foldr]

I don't have a definition of 'pro', and my point is not based on any assumptions about what the word means. I don't care how the Apple marketing department decides to name their laptops, and I can't imagine why anyone else would either.