This is the curse of being an expert (on anything) and engaging with kooks who think they are experts because they read something on the internet.
If you had direct experiences and you share them, those shouldn't be ridiculed, but if you pass on information that is not from your direct experience and which people who have direct experience believe to be false... that's also, as you say, "not a good look".
Then they go on to say "I mean my sources are the actual 5G Standards," - And it's never been the case that a standards document sounds great, but doesn't work well or is implemented badly? Or tries to address a problem but doesn't? "and on implementing electronics" - so not actual experience of trying it?
What someone says gives a very strong signal for where they heard it.
Yes, you could perhaps challenge the relevance of the standards here, but to do that, you would need to provide strong evidence.
"I heard someone used it and it didn't work well" is the same level of evidence as product reviews, and is strong enough for all of us to make day to day judgements on. "I read the spec and the spec says it should be good" is not strong evidence - all spec would say that, or be revised until it said that. Yet still bad products abound.
If I take your position as stated: 1) Those claims, by the time they to us, are hearsay and therefore have no value. 2) An Intel engineer stating that they have more knowledge and it should work well, is not hearsay and does have value. 3) Whether the Intel engineer respects the reader or not, matters.
Am I misrepresenting anything in your position here? If not, then I feel the opposite about all three points. This isn't about engineer vs user's knowledge, it's about differences between design-intent and real-world result.
Yes.
1) I never said "no value". The claims have value. Call it 2 bits per claim, with diminishing returns after the first few.
2) The Intel engineer has considerably more context, and more on the line, so their claim has considerably more weight. Call it... 8 bits. If they say it should work, then it should work, and if other people say it doesn't work, that doesn't mean someone is wrong, it might just mean that it should work, but for someone it isn't working, for whatever other reasons.
3) If the Intel engineer tells you your opinion is wrong or out of date, you should probably give that considerably more weight than if some random person on the internet without that context says it.
The engineer working in the field can be expected to know a lot more about both the intended design, the actual build, and the real-world issues arising in practice compared to what any individual user would know about any of those things. This is generally why experts don't like to engage with non-experts; the non-experts' priors on who to trust are likely to be all out of whack.
Why would that be "despite"? That would have to be being confident in its failure despite having information that it would be a success. Surely they're confident in its failure because the information they have says it will be bad?
And then your comment becomes "I'm laughing because you're confident in your beliefs" which is content-free smugness, or "I'm laughing at you because you don't know what I know" which is more or less the same, if not worse.