3 ms·

Not all, or even most complaints I've seen is from 'those' groups, whatever that is supposed to mean exactly, are enthusiast really the worst issue with persoba

Not all, or even most complaints I've seen is from 'those' groups, whatever that is supposed to mean exactly, are enthusiast really the worst issue with persobal computers ? Back to the issue, most complaints I've seen/heard are from actual professionals who wants - or needs - magsafe, more RAM, more ports, more storage, more speed, or better batterylife. The new MBP doesn't give you much more than what you already have, and for people having machines starting to wear out, buy another of essentially the same thing feels like a bad deal. For me personally the biggest issues are magsafe and no RAM upgrade beyond 16GB. I simply run out of RAM all the time, but I would prefer not having to switch to windows simply to get more than 16GB RAM, with all the pain that would entail. Magsafe because it have saved my machine several times while on the road or working from home with kids running around.

acdha 10y ago
I've heard a lot of people cite their with as why they need more capacity but most of them go silent when asked to explain e.g. what they can do with 32GB but not 16GB (exceptions were edge cases like someone who worked on a model which was ~20GB), a gaming-class GPU, why Kalby Lake is a requirement, etc. I'm actually in the camp which would prefer more battery but this seems more like the effects of forum echo chamber reinforcement than anything like a strong trend.
- swozey 10y ago
  32gb vs 16gb for me is the difference between having my local development environment a replica of production EXCEPT massively scaled down vertically and horizontally. Meaning I can still have clustered databases (couchbase, etc) to test against vs having to test against an environment that has zero clustering at all. This might be fine for some, but there are a lot of gotchas that you encounter when dealing with disparate query + index servers that you wouldn't ever run into if you completely wrote code against a single instance. Sure, this is an edge case but that doesn't minimize my requirements for 32gb of ram. I'll be buying a new laptop next year to replace my 2015MBPr and it will definitely be one that has 32gb minimum. That is, at this point, more important by far than OSX to my workload.

acdha 10y ago

I've heard a lot of people cite their with as why they need more capacity but most of them go silent when asked to explain e.g. what they can do with 32GB but not 16GB (exceptions were edge cases like someone who worked on a model which was ~20GB), a gaming-class GPU, why Kalby Lake is a requirement, etc. I'm actually in the camp which would prefer more battery but this seems more like the effects of forum echo chamber reinforcement than anything like a strong trend.

swozey 10y ago
32gb vs 16gb for me is the difference between having my local development environment a replica of production EXCEPT massively scaled down vertically and horizontally. Meaning I can still have clustered databases (couchbase, etc) to test against vs having to test against an environment that has zero clustering at all. This might be fine for some, but there are a lot of gotchas that you encounter when dealing with disparate query + index servers that you wouldn't ever run into if you completely wrote code against a single instance. Sure, this is an edge case but that doesn't minimize my requirements for 32gb of ram. I'll be buying a new laptop next year to replace my 2015MBPr and it will definitely be one that has 32gb minimum. That is, at this point, more important by far than OSX to my workload.