As it says in the title, I'm stuck between at 14" M3 Max (binned) and a 16" M3 Pro (full bore).
My primary use case is Software Development, but I'm not working on massive data operations. The main thing I'm concerned about is having enough memory, so 36" is my target memory configuration, and I'm totally willing to stick with 512GB storage.
Given those constraints, the price difference between the 12-core M3 Pro and the 14-core M3 Max is about the same as the difference between the 16" and the 14" models. These are about at the limit of my budget.
14" M3 Max - 14-core - 36GB/512GB - $2999
16" M3 Pro - 12-core - 36GB/512GB - $2899
(Full disclosure, I already have the 16" -- this would be a matter of return + reorder)
Reasons to want the 14":
My primary use case is Software Development, but I'm not working on massive data operations. The main thing I'm concerned about is having enough memory, so 36" is my target memory configuration, and I'm totally willing to stick with 512GB storage.
Given those constraints, the price difference between the 12-core M3 Pro and the 14-core M3 Max is about the same as the difference between the 16" and the 14" models. These are about at the limit of my budget.
14" M3 Max - 14-core - 36GB/512GB - $2999
16" M3 Pro - 12-core - 36GB/512GB - $2899
(Full disclosure, I already have the 16" -- this would be a matter of return + reorder)
Reasons to want the 14":
- Portability. I have a 14" M1 Pro and it's quite a bit more light and compact.
- Most of the time, I'm docked and working on two external monitors (wide and tall orientation). The MBP is sitting to the side as my third monitor.
- Significant CPU increase over the M3 Pro.
- I really like the 16" screen. I have a 14" M1 Pro and the screen real estate difference is significant.
- Most of the time, I'm docked and working on two external monitors, so the portability of the smaller laptop is irrelevant.
- Larger battery
- Better cooling. I've heard anecdotes of throttling and runaway fans on 14" max models.
- My work involves quick cycles of build/deploy/test, which are typically not huge CPU activities, so a CPU increase may not be a huge factor in my workload.