What's your opinion on the MacBook Pro not being a professional's computer?

[stuartfang]

The original Reddit post says "not for Photographers or Video Editors," how does OP come up with such a generalized statement about a computer that has the word "Pro" in its name not being used by pros?

Apple did not create the MacBook Pro line intending for it to only be used by professionals. Therefore this thread is invalid and OP's topic of discussion has no meaning. Request any moderator to lock this thread inb4 it becomes toxic.

Case Closed

 

[theSeb]

I am a professional and I use an rMBP. Should I stop and throw it away immediately? Please advise as soon as possible. Thanks.

 

[alkalifly]

I am a professional and I use an rMBP. Should I stop and throw it away immediately? Please advise as soon as possible. Thanks.

I don't think it matters whether or not you are a professional whatever. The issue is whether or not the rMBP is a professional computer. So, if your rMBP makes its living as a computer, it is a professional computer, but if it makes its living waiting tables, driving a cab, or teaching school, then being a computer is just a hobby

 

[theSeb]

I don't think it matters whether or not you are a professional whatever. The issue is whether or not the rMBP is a professional computer. So, if your rMBP makes its living as a computer, it is a professional computer, but if it makes its living waiting tables, driving a cab, or teaching school, then being a computer is just a hobby

This makes sense to me. Thank you.

 

[john123]

John,

Perhaps you had trouble reading. This topic is not about discussing Xen server setups, so your post appears to be "trolling" in regards to making superfluous remarks.

Let's review the facts, shall we?
• You posted a thread about whether or not the MBP is a "professional's computer"
• A poster cited a professional use case
• You claimed that the MBP is not good for that use case
• The poster told you you have no idea what you're talking about

That's not trolling, nor is it superfluous. It is entirely on point. I suspect you don't know what trolling is.

It has nothing to do with this topic. He just feels threatened, like others who have called me a "troll"

I can't speak for all of us, but I know that at least many of us do not feel threatened. We just disagree with your position and believe you are making a mountain out of molehills.

 

[Macshroomer]

Request any moderator to lock this thread inb4 it becomes toxic.

12 pages of MacSumo wrestling would make it toxic in my estimation.

 

[undesign]

My MacBook Pro, early 2011 overheated after taking a major beating with After Effects and converting 720p and 1080p movies with Handbrake. The GPU in it fried.

Is the MacBook Pro for professionals? Well... its certainly capable in terms of power... but I don't trust it anymore.

 

[Ryan1524]

12 pages of MacSumo wrestling would make it toxic in my estimation.

Are you kidding? This is pure entertainment. And highly instructional as a cautionary tale.

As for 'professional' tools, ALL work-assigned laptops and desktops in my office are roughly 3x slower with smaller screens and 30% heavier. They get replaced every 2-3 years.

The professions define the tools, not the other way around.

 

[john123]

My MacBook Pro, early 2011 overheated after taking a major beating with After Effects and converting 720p and 1080p movies with Handbrake. The GPU in it fried.

Is the MacBook Pro for professionals? Well... its certainly capable in terms of power... but I don't trust it anymore.

I'm curious. How do you know it "overheated"? And how do you know those things were the cause?

 

[undesign]

I'm curious. How do you know it "overheated"? And how do you know those things were the cause?

I did my research. It was definitely the GPU; grey lines at boot screen, CLASSIC example of GPU failure.

It finally crapped out when I was watching a flash video stream of a basketball game.

 

[john123]

I did my research. It was definitely the GPU; grey lines at boot screen, CLASSIC example of GPU failure.

It finally crapped out when I was watching a flash video stream of a basketball game.

I actually wasn't questioning whether it was the GPU that failed. I was questioning your hypothesis as to why (specifically, the load/heat).

 

[theSeb]

I did my research. It was definitely the GPU; grey lines at boot screen, CLASSIC example of GPU failure.

It finally crapped out when I was watching a flash video stream of a basketball game.

So your computer did not over heat and it was actually the gpu that failed. Thanks for the confirmation that your previous post was nonsense.

 

[undesign]

So your computer did not over heat and it was actually the gpu that failed. Thanks for the confirmation that your previous post was nonsense.

https://forums.macrumors.com/threads/1681439/

I recommend you don't come off so pompous. Sorry bud, you're wrong.

----------

I actually wasn't questioning whether it was the GPU that failed. I was questioning your hypothesis as to why (specifically, the load/heat).

Its a known issue, see my reply above.

 

[bill-p]

https://forums.macrumors.com/threads/1681439/

I recommend you don't come off so pompous. Sorry bud, you're wrong.

----------



Its a known issue, see my reply above.

Just on a side note, GPU failure may be caused by a number of things, and not necessarily as a result of excess heat.

In most cases (that I have observed), it's actually because the solder joints on the GPU were bad to begin with. Long term operation of the computer would eventually cause these solder joints to either short out, or go... disconnected entirely. In which case, the GPU is not getting the right signals in order to operate anymore, and it fails.

You may argue that excess heat accelerated the failing process, which is true, but heat is only part of the problem. Any amount of heat (high or low) would have caused about the same amount of damage.

So technically, it's not an "overheat" issue, or at least not in the same sense as "if you exceed X degrees Celsius then the GPU fails". It's more a case of "the GPU will fail faster if there is more heat, but it will fail anyway at some point".

 

[phsphoenix]

Let's review the facts, shall we?
• You posted a thread about whether or not the MBP is a "professional's computer"
• A poster cited a professional use case
• You claimed that the MBP is not good for that use case
• The poster told you you have no idea what you're talking about

That's not trolling, nor is it superfluous. It is entirely on point. I suspect you don't know what trolling is.


I can't speak for all of us, but I know that at least many of us do not feel threatened. We just disagree with your position and believe you are making a mountain out of molehills.

It's more like he's making mountains out of individual carbon molecules. I mean, if he's really a professional using the computer as a tool, a fully speced rmbp should be pocket change for the company that employs him. In fact I'm pretty sure HP and Dell charge more if you want their mobile workstations designed for 3D graphics professionals, and a lot of places use those. The fact that he's whining leads me to believe that he's either a student who thinks he knows best because he studies computer science or has some experience in the field, or he just has a severe case of tunnel vision.

 

[john123]

https://forums.macrumors.com/threads/1681439/

I recommend you don't come off so pompous. Sorry bud, you're wrong.

----------



Its a known issue, see my reply above.

There's a certain irony in calling someone "pompous" and then calling them "wrong," especially when there is a good possibility their claim is correct and yours is wrong.

You have committed a pretty egregious logical fallacy. You assume that your GPU failure is due to overheating. That is speculation, not fact. In fact, you might even have the causal relationship reversed: a bad GPU could cause the thermal problems. bill-p's comment above suggests one way in which this could work.

I'd think twice before you levy the "pompous" claim again.

----------

The fact that he's whining leads me to believe that he's either a student who thinks he knows best because he studies computer science or has some experience in the field, or he just has a severe case of tunnel vision.

I think you're giving him too much credit. I rattled off a Terminal command specifically designed to push all the cores as hard as possible (yes > /dev/null), and his response was that I needed to run After Effects for a "real world" test to see the temperatures he claimed. He clearly didn't know what the command did, and that's something an Intro to CS student would know.

 

[phsphoenix]

There's a certain irony in calling someone "pompous" and then calling them "wrong," especially when there is a good possibility their claim is correct and yours is wrong.

You have committed a pretty egregious logical fallacy. You assume that your GPU failure is due to overheating. That is speculation, not fact. In fact, you might even have the causal relationship reversed: a bad GPU could cause the thermal problems. bill-p's comment above suggests one way in which this could work.

I'd think twice before you levy the "pompous" claim again.

----------



I think you're giving him too much credit. I rattled off a Terminal command specifically designed to push all the cores as hard as possible (yes > /dev/null), and his response was that I needed to run After Effects for a "real world" test to see the temperatures he claimed. He clearly didn't know what the command did, and that's something an Intro to CS student would know.

Ok then, so 15 year old who doesn't want to spend all the cash he earned last summer on anything but what the "experts" say is the very best computer for all situations ever. At the same time he wants Mac OS X on it.

Which reminds me, maybe we can get him to run this :

int main() { while(true) { int* pointer = new int; } return 0; }

Let's see how long it'll take for him to tell me that I don't know what I'm doing.

 

[undesign]

int main() { while(true) { int* pointer = new int; } return 0; }

Let's see how long it'll take for him to tell me that I don't know what I'm doing.

 

[bkribbs]

Not to add to all this but I want to ask- I purchased BF4 and it runs great on medium settings, but it runs hot. According to icorestat or whatever that app is on windows that I have also seen in this thread, my 2012 rMBP CPU is between 95-105 (tjunction for my CPU is 105) so is that heat bad? Or bad for the surroundings?

I'd love to reapply thermal paste but I don't want to void my warranty.

 

[john123]

Not to add to all this but I want to ask- I purchased BF4 and it runs great on medium settings, but it runs hot. According to icorestat or whatever that app is on windows that I have also seen in this thread, my 2012 rMBP CPU is between 95-105 (tjunction for my CPU is 105) so is that heat bad? Or bad for the surroundings?

I'd love to reapply thermal paste but I don't want to void my warranty.

I wouldn't reapply paste unless you're out of warranty. Getting values approaching Tjunction isn't really a problem because the processor is going to throttle itself/not TurboBoost as necessary anyway. So, unless you're finding performance to be unacceptable (i.e., you need things to run cooler so the processor can kick things up a notch), I wouldn't worry.

 

[Mr. Retrofire]

I actually wasn't questioning whether it was the GPU that failed. I was questioning your hypothesis as to why (specifically, the load/heat).

It is not his hypothesis. It is a well known problem. The same happened on some 2007, 2008, 2009 (17" in my case) MBPs.

 

[undesign]

There's a certain irony in calling someone "pompous" and then calling them "wrong," especially when there is a good possibility their claim is correct and yours is wrong.

You have committed a pretty egregious logical fallacy. You assume that your GPU failure is due to overheating. That is speculation, not fact. In fact, you might even have the causal relationship reversed: a bad GPU could cause the thermal problems. bill-p's comment above suggests one way in which this could work.

I'd think twice before you levy the "pompous" claim again.

There's no speculation on what happened to my MacBook. All the reports online suffered with the same problem as mine, and an Apple tech confirmed it as well when I had it fixed.

I'll continue using the pompous claim, thank you very much.

 

[john123]

It is not his hypothesis. It is a well known problem. The same happened on some 2007, 2008, 2009 (17" in my case) MBPs.

No, no, and no. Please read, because you aren't getting it. The well known problem is problematic GPUs (I have a 2008 with the same problem). The OP has alleged that high temperatures led to that problem, and I'm disputing his theory. The OP knows a few facts and is using them to make an invalid causal inference (actually, multiple invalid causal inferences). This is Logic 101. The facts he knows are:
• His GPU failed
• His temperatures spiked prior to the failure
• Many other users had GPU failures and spiking temperatures

The problems with his theory—that high temperates led to his GPU failure—are manifold:
• It assumes that high temperatures caused the failure, which is not deterministically proven
• It ignores another hypothesis: that the failure was due to an innate defect that had, as a byproduct, high temperatures
• It generalizes evidence from the aggregate to the specific. In other words, even if the prevailing theory that high temperatures were causing GPU failures is correct, it is presumptive to assume that the same thing happened to his machine (i.e., failure to exclude other hypotheses)

----------

There's no speculation on what happened to my MacBook. All the reports online suffered with the same problem as mine, and an Apple tech confirmed it as well when I had it fixed.

You're just making stuff up at this point. I believe that an Apple Tech confirmed your GPU failed. I do not believe that he confirmed it was "due to" high temperatures (or if he really did say that, I posit that he didn't know what he was talking about).

Your lack of reading comprehension is leading you to superimpose your theory onto "all the reports online" that you're reading.

If you're unable to grasp this...well...I guess that sucks for you. There's only so many times you can lead a horse to water before you might as well just euthanize him.

 

[undesign]

No, no, and no. Please read, because you aren't getting it. The well known problem is problematic GPUs (I have a 2008 with the same problem). The OP has alleged that high temperatures led to that problem, and I'm disputing his theory. The OP knows a few facts and is using them to make an invalid causal inference (actually, multiple invalid causal inferences). This is Logic 101. The facts he knows are:
• His GPU failed
• His temperatures spiked prior to the failure
• Many other users had GPU failures and spiking temperatures

The problems with his theory—that high temperates led to his GPU failure—are manifold:
• It assumes that high temperatures caused the failure, which is not deterministically proven
• It ignores another hypothesis: that the failure was due to an innate defect that had, as a byproduct, high temperatures
• It generalizes evidence from the aggregate to the specific. In other words, even if the prevailing theory that high temperatures were causing GPU failures is correct, it is presumptive to assume that the same thing happened to his machine (i.e., failure to exclude other hypotheses)

----------



You're just making stuff up at this point. I believe that an Apple Tech confirmed your GPU failed. I do not believe that he confirmed it was "due to" high temperatures (or if he really did say that, I posit that he didn't know what he was talking about).

Your lack of reading comprehension is leading you to superimpose your theory onto "all the reports online" that you're reading.

If you're unable to grasp this...well...I guess that sucks for you. There's only so many times you can lead a horse to water before you might as well just euthanize him.

Are you trying to argue for the sake of arguing? Get over yourself.

 

[Mr. Retrofire]

...
Which reminds me, maybe we can get him to run this :

int main() { while(true) { int* pointer = new int; } return 0; }

Let's see how long it'll take for him to tell me that I don't know what I'm doing.

You do not know what you are doing, because you do not need the two "{}" after the "while(true)" statement, if the while loop has only one line.



This is enough:

int main(void) { while(1) int* pointer = new int; return 0; }

----------

No, no, and no.

I've the first hand experience and he too.