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

Fit of the CoreWCF Question on StackOverflow

• Some argue the original question was legitimately “not a good fit” for SO: it was an open‑ended debugging/performance problem (“high CPU”), spanning a lot of code and likely needing back‑and‑forth, not a single focused question.
• Others counter that it was clearly technical, reproducible, and had a concrete failure condition, and that difficult or niche issues should still belong on SO.
• There’s detailed explanation of SO’s expectations: minimal reproducible examples, prior profiling/analysis, and isolating one precise question rather than posting a whole problem.
• The question was eventually edited (more specific title, profiling info) and reopened, which defenders say is exactly how the close–edit–reopen process is supposed to work.

CoreWCF / WCF Streaming Behavior

• Multiple commenters suspect the server keeps writing to an infinite stream after the client disconnects, never reaching EOF, leading to persistent CPU use.
• Suggested fixes include:
  • Using CancellationTokens and communication-object events (Closed, Faulted) to stop the stream and return EOF.
  • Custom stream implementations that check a “client still connected” flag and immediately return 0 bytes when false.
  • Overriding Close/Dispose where meaningful, though some note the custom stream doesn’t own resources.
• Others note WCF/CoreWCF’s streaming is designed for finite-length messages terminated by EOF; unbounded streams are effectively outside its intended model and may expose bugs.
• Several people recommend reporting this on the CoreWCF GitHub issue tracker or discussions, where similar streaming bugs already exist.

StackOverflow Culture, Moderation, and Decline

• Many report leaving or posting far less due to: aggressive closing/duplicate marking, deleted content, hostile tone, and “bureaucratic” rule enforcement, especially on niche or sophisticated questions.
• Others defend the curation: SO is meant as a high‑quality, searchable knowledge base, not a general helpdesk. Closing quickly is seen as necessary to keep out low‑quality/duplicative debugging questions.
• There is extensive debate over duplicates, reputation incentives, and the distinction between community curation vs elected moderators. Some see a small core “defending the vision”; others see an in‑group driving away regular users.

LLMs and Alternative Channels

• Several commenters now prefer asking LLMs: instant, polite answers, no downvotes or closures—while acknowledging answers must still be verified.
• It’s observed that LLMs partly rely on SO content; SO, in turn, bans AI‑generated answers and has bulk‑deleted some for that reason.
• Others suggest GitHub issues/discussions, project trackers, or alternative Q&A platforms as better venues for complex, project‑specific debugging.