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.<p>Screaming into the void of the blogosphere is catharsis for getting my SO question closed.<p>And because I know you're all nosy, the SO question is here: <a href="https://stackoverflow.com/questions/79605462/high-cpu-usage-in-corewcf-after-streaming" rel="nofollow">https://stackoverflow.com/questions/79605462/high-cpu-usage-...</a> . Please feel free to point out more ways in which I screwed up asking my SO question.
My most recent (nearly 3 years ago) StackOverflow story:<p>I posted a question[1]. Got some answers, but not quite complete. Then someone came along and provided a good detailed answer. A couple of upvotes later, that answer got deleted by Community Bot. I voted to undelete it, but it still needs another vote to undelete. So I ended up copying it into my own notes blog[2].<p>I'm not sure why the best answer was deleted. It would've been a loss if it wasn't preserved somewhere I think.<p>[1]: <a href="https://stackoverflow.com/q/73954228/155351" rel="nofollow">https://stackoverflow.com/q/73954228/155351</a><p>[2]: <a href="https://notes.max.engineer/creating-common-interfaces-in-golang" rel="nofollow">https://notes.max.engineer/creating-common-interfaces-in-gol...</a>
I used to be very active on StackOverflow, it was a great platform.<p>After a while, I stopped having to post questions about "common frameworks", either because I could do with the official docs of because there was already a StackOverflow answer for my question.<p>What was becoming more common was that I would have a question similar to an existing unanswered one. Or that my question would never receive an answer (presumably because my questions were becoming more tricky/niche). So what I started doing was answering my own question (or answering those existing unanswered ones) after solving it on my own. Still, it was fine and I was contributing.<p>And for some reason, a few years ago my questions started being closed for no apparent reason other than "those who reviewed it have no clue and think that it is invalid". Many times they closed even though I had posted both the question and the answer at the same time (as a way to help others)! The first few times, I fought to get my question reopened and guess what? They all got a few tens of votes in the following year. Not so useless, eh?<p>Still, that toxic moderation hasn't changed. If anything, it has gotten worse. So I stopped contributing to StackOverflow entirely. If I find information there, that's great, if not, I won't go and add it once I find a solution for myself. I am usually better off opening an issue or discussion directly with the upstream project, bypassing StackOverflow's moderation.<p>I heard people mentioning that LLMs were hurting StackOverflow badly. I'm here to say that what pushed me away was the toxic moderation, not LLMs.
Stack Overflow is like online gaming -- lots of toxic people, but I still get value out of it.<p>Ask a question.<p>Ignore the trolls.<p>Get a question answered that would have taken you another day to solve.<p>Make money.
Stackoverflow is no longer a Q&A site. It's trying to become a curated information source. Like wikipedia or the kind of thing you'd train AI with. As such it isn't great for answering question any more.<p>Another old problem was notable users. There was a guy famous for his presence and answering tons of question (I forgot his name). He was actually pretty good but... he was not an expert in all the areas he'd participate in, but his answers would sometimes win because he was articulate, not because it was the best.
There are some events you can handle:<p><a href="https://learn.microsoft.com/en-us/dotnet/api/system.servicemodel.icommunicationobject.closed" rel="nofollow">https://learn.microsoft.com/en-us/dotnet/api/system.servicem...</a><p><a href="https://learn.microsoft.com/en-us/dotnet/api/system.servicemodel.icommunicationobject.faulted" rel="nofollow">https://learn.microsoft.com/en-us/dotnet/api/system.servicem...</a><p>Could you use these to cancel the stream?
Looks like the framework is just going to keep reading to the end of the random number stream, but of course there isnt an end to it.<p>Is there some kind of `IClosableStream` you can implement? That’d give you a `Closed` method, which you can then use to let either your server or stream know that it’s time to stop reading (or the stream reached EOF) - even if it’s done with a flag that’s set when the client disconnects.<p>Maybe there’s already an optional `Close` method you’re not overriding?
StackOverflows days are numbered, the site isn't like it used to be, it used to be useful, but over time people spend more time trying to game the system or enforce their own interpretation of rules.<p>SO is trash now-a-days.
I opened my SO account 15 years ago and I was liking the dynamics very much.<p>Now at 200k+ rep I cannot stand it anymore. Whenever I ask a question that does not make me bow backwards or discuss how my Python code looks in assembly it gets downvoted almost immediately. Go and Typescript are tags that being frustration.<p>Now compare this with many other Stack Exchange sites.<p>A question about cooking or LaTeX gets nice, coloriant answers, even when they are basic.<p>I get it that they are one or two orders of magnitude less crowded but this may mean that SO passed its scale limit and is done.
If the author reads HN comments - findings like these are probably better to be submitted at <a href="https://github.com/CoreWCF/CoreWCF">https://github.com/CoreWCF/CoreWCF</a> instead<p>(although I have no idea how active CoreWCF owners are w.r.t this)
> This is confusing enough for humans, let alone a machine that will happily reproduce calls and configuration from something that is almost identical, yet subtly different and incompatible.<p>Interesting point. I'm going to see if they similarly struggle generating VBA code vs generating Visual Basic code.
I have been an SO user for 13 years with around 9k karma. I have recently started having similar negative experiences.<p>I posted this iOS Swift Programming question today:<p><a href="https://stackoverflow.com/questions/79612931/ios-custom-operation-for-operation-queue-gives-warning-class-must-restate-inheri" rel="nofollow">https://stackoverflow.com/questions/79612931/ios-custom-oper...</a><p>and was instantly downvoted and then voted to closed. I do not think this question was worth downvoting or closing. There's no hits on the warning I was getting.<p>People on SO nowadays seem way too eager to downvote and close.
C# is not my primary language but have the misfortune of debugging C#/.Net junk.<p>Seems like an issue with not closing resources properly. Looking at your server code, seems the Close and Dispose methods are not overridden. Try that?