Usually when I have a question that I cannot find the answer to by searching for it, it is utterly misunderstood. Example: Today I asked why the proxy pattern was so slow in java, in the case of wrapping tiny methods, as done in real programs (not microbenchmarks). There are several problems with this question:
- If you use a microbenchmark, it's simple enough for Hotspot to figure things out and it not be slow.
- Proxies only add significant overhead if the wrapped methods are tiny, which they usually are not.
- Saying something that sounds anything like "known good practice is bad" makes me sound like a clueless newb, and people respond to that without reading the question deeply enough to see that it's actually "in certain edge cases, known good practice is bad. Why?"
- I neglected to initially provide any reference for my seemingly absurd claim. That was just dumb of me.
- It's a question about performance. The typical SO user is (reasonable) virtually allergic to such questions, since new programmers ask OH SO MANY premature-optimization questions.
- I remember thinking of more problems. But I don't remember what they were =(
Is there any way I can ask unintuitive questions like that and get an answer instead of being turned away frustrated?