←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: 0s | 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 #
matsemann ◴[08 May 25 12:58 UTC] No.43925669[source]▶
Honestly, I agree with it not being a good fit for a Q&A site. It's a debugging problem, probably needing a discussion, and might even not be of any use to others being that "high cpu" is kinda vague. Seems better suited for a bug report / issue tracker of the relevant library.
replies(5): >>43925828 #>>43925881 #>>43925895 #>>43926071 #>>43932335 #
1. francisofascii ◴[08 May 25 13:47 UTC] No.43926071[source]▶
I could see it being useful to others. If there is an internal bug that causes the issue or even a code pitfall that causes this issue.