StackOverflow's questions per day have fallen 99%
meta.stackoverflow.com
meta.stackoverflow.com
I presume this happens nowadays frequently. All easy questions are answered by chat-bots or have ben already answered and hard questions don't pass gatekeeping.
Outdated OS can be the problem as well.
What kind of advice did you expect?
It's a lot of work of rewriting it in C. It's doable, but impractical. And such rewrite may introduce new bugs.
Proving that the problem isn't in my language wasn't necessary - there were no room for it to introduce such kind of bug. Language bugs are usually manifest themselves in a way different way, (like broken binary code leading to crashes or accepting invalid code). That's why I have created my question in a first place - while I was sure, that it wasn't a language bug.
> Outdated OS can be the problem as well.
Outdated OS can't be a problem. Basic socket functionality was implemented eons ago and all known bugs should be fixed even in pretty outdated versions of the kernel.
> What kind of advice did you expect?
Eventually I have found myself, that in my test program I create too much connections for a TCP server and its internal connection queue overflows. But it took some time to find it, way longer compared to what could be achieved if my SO was answered. The problem was not so hard to spot considering that I have described what exactly I do. Even providing code examples wasn't necessary - textual description was enough.
Could very well be that your language was the issue and writing a small proof of concept for the specific use case that's problematic in a battle tested language other people know is a standard trouble shooting step. Especially if it was a rare limiting error, that sounds like a trivial thing to be implemented in C with a simple for loop and some dummy data perhaps.
Same with the OS. Only because socket functionality is decades old doesn't mean that you can't hit a recently introduced bug, that could have been fixed in a new version. That also is a standard troubleshooting step.
It doesn't make for bad advice only because you're too lazy to do it.
The website was sold to Prosus, a Netherlands-based consumer-internet conglomerate, on 2 June 2021 for US$1.8 billion.[10]
I'm guessing if Stackoverflow is sold now, it'd be worth $1.8m instead of $1.8b.
On the site itself, the opinion seems to be that stackoverflow is not dead and it's okay if there's reduced traffic and questions to the site.
Yet off site, the opinion is that stackoverflow is dead and added to that, the community isn't very friendly anymore.
It's just really interesting to see the perspectives between the two.
Average programmer: It's dead.
Stackoverflow management: It's dead.
A major focus of AI companies will be to seek precious pre-slop data, a bit like low-background steel. Krazam has a skit about this.
Stack overflow is almost dead
https://news.ycombinator.com/item?id=43999125
Some more recent discussion on that chart:
Total monthly number of StackOverflow questions over time
I wonder what other human lasts have happened since AI.
The new activity in stackoverflow is only for really novel questions. We’ve effectively automated a lot of labour here. Isn’t that nice?