←back to thread

My stackoverflow question was closed so here's a blog post about CoreWCF

(richardcocks.github.io)
123 points eterm | 1 comments | 08 May 25 12:11 UTC | HN request time: 0.2s | source
Show context
eterm ◴[08 May 25 12:11 UTC] No.43925356[source]▶
A post in which I try to rubber-duck a CoreWCF issue I've been having, because stackoverflow no longer seems suitable for asking questions about programming issues.

Screaming into the void of the blogosphere is catharsis for getting my SO question closed.

And because I know you're all nosy, the SO question is here: https://stackoverflow.com/questions/79605462/high-cpu-usage-... . Please feel free to point out more ways in which I screwed up asking my SO question.

replies(10): >>43925551 #>>43925669 #>>43925930 #>>43925975 #>>43926332 #>>43927351 #>>43931071 #>>43933405 #>>43933839 #>>43935803 #
balls187 ◴[08 May 25 13:28 UTC] No.43925930[source]▶
I don't see anything wrong with your SO question (I am a long time contributor), and don't see why it would have been closed.

I will say, this is a level of question that is too sophisticated for SO, and likely will only have an answer once you figure it out and go back and answer your question.

Are you confident the code is the issue--have you repro'd it consistently with different versions of .NET? What about reproing on different machines? Locally?

replies(2): >>43933418 #>>43933907 #
1. rendaw ◴[09 May 25 02:55 UTC] No.43933418[source]▶
Do they have some metric whereby all questions must be answered in some time period? Why not just leave it open then? What if someone else has the same question and figures it out later, now they can't answer it either!

I had the same suspicion though, which is that if the question is too difficult it triggers some reflex...