William Kucharski wrote:
ryunokokoro wrote:
William, do you not understand how continuously pointing out your own experience in this thread causes them to feel as though you're discounting their experience?
Not at all.
Science - which computer science is - requires reporting of all results, positive and negative.
Further, the fact that my configuration does not experience the issue does not belittle those experiencing the issue, but rather shows there is some further, non-obvious factor that explains is part of the issue.
I think you missed the point. I never said that your goal was to discount others' experiences. Rather, I pointed out that your statements are received as belittling. This is a human thing, not a "facts" thing.
I agree that your data point should not be discounted. It is important and I assume that Apple themselves already have many such examples in-house. As they are "aware of the issue" and "the behavior is expected", they clearly have examples in house that replicate the issue as well. Apple has the data. This forum is for the users. Help the users. There are two ways to do this:
- Point out the root cause of the issue (GPU "quirks") and suggest that they fiddle with settings to see if they can get an improvement. Reporting working results/configurations will help with this.
- Tell them to contact Apple Support.
If your reaction is to suggest contacting support, then I'm not sure how much help it is to even bother getting into the root cause explanation stuff.
You and everyone else here may be able to see the issue, but unless it can be reproduced in-house, it will end up marked "cannot reproduce" as there's nothing to go on to reproduce it. Anyone who has ever developed and debugged software has been there.
I do not have a 16" laptop. I have the 2018 15" laptop. I found this thread while looking for details related to [an apparently different] issue my laptop was having.
We also already know that this isn't a "cannot reproduce" problem for Apple as they have reported that this is "expected behavior". They can certainly reproduce it. They just don't have any way to (or plans to) "fix" it.
Anyone who has developed and debugged software has also been in the situation where they find that something working in a less-than-ideal fashion is actually working "as designed". Which you've already pointed out is what Apple has said.
Talking about Apple filing this as "cannot reproduce" in this case is a red herring to the conversation.
People find this thread looking for help; for a solution. When you chime in with "Well, it doesn't happen for me. My GPU draws 20W and yet my fans stay at a cool 2400 RPM!" there is an implied "***** to be you!" You may not intend this, but it is how it comes off.
That's your read of the situation, not the read of anyone looking at it in an objective, scientific way.
You are on an internet forum for general users. While there are some who may come and be Vulcan-level in their objective, logical view of things, most people come to this thread upset that they've spent thousands of dollars on a machine that they expected would be able to handle external monitors at least as well as their previous machines. They are very likely not looking at this in a purely objective way, but rather a passionate one where they desperately want their investment to work as they expected.
It doesn't take much to determine that most people chiming in on this thread are upset in this way. The language they use is rife with disappointment and emotion. Engaging them on that level and working with them (e.g. "I am very sorry to hear that you're having this issue. Rest assured this doesn't appear to be a universal thing so there is likely a way that your machine can get whisper quiet as well. To start, can you tell us what your display configuration is? The more details, the better!") will be more effective than purely stating facts at them (e.g. "This does not occur for all 16" laptops. My laptop proves that. This is a GPU related issue and it is expected behavior.").
I want to see who has the issue, who doesn't and look for the differences, as therein lies understanding of the issue.
That's... kind of an odd statement to make. Anyone the vast majority of people chiming in here do so because they are having the problem listed in the thread title. So identifying this part is trivial.
As for "looking for the differences", I agree 100% with this. I looked back through the last several pages of this thread (5 pages, at least) and didn't notice you request such data. Did I miss something?