To be clear, I don’t think the person is stupid, and I don’t believe I’ve called them stupid. I appreciate the intent to support me, but I also find it a bit of a stretch that answering “is DO_NOT_USE supported” with “no, it’s not supported” must be a consequence of a culture shock. :) But I’m biased so idk.
I didn’t get the impression from the reader that they were a beginner, or someone struggling, or someone who doesn’t “know they’re on the wrong path”. My impression was that a professional came to get an authoritative answer on a level of support of an API, and I tried to provide it.
Oh, I didn't think you were calling them stupid! That's part of what I mean as the culture shock - that Westerners will respond to being told they're doing something stupid as if it was an insult to themselves, and not an insult on what they're doing, disregarding the fact that smart people can do stupid things and vice versa. What the OP was trying to do _is_ stupid, but that doesn't make them a stupid person. They could in fact be a very experienced engineer who has delivered beautiful and capable web apps. I don't believe your intent was to make the OP feel stupid, but perhaps the lack of sugarcoating and straightforwardness of your response makes it seem like that. I don't think you were impolite either, it's just that terse responses usually signal impatience and may get misconstrued as anger, despite the intent being to clearly communicate a simple message.
Fair enough! I feel like with questions like this, there is a lot at stake because they will be referred to in conversations (“should we use this field? seems like it’s no big deal”) so perhaps some of the bluntness of the property name rubbed off on my response.
I didn’t get the impression from the reader that they were a beginner, or someone struggling, or someone who doesn’t “know they’re on the wrong path”. My impression was that a professional came to get an authoritative answer on a level of support of an API, and I tried to provide it.