The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I agree to 100% with OG.
And add "Don't take it too seriously... not worthy at all."
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
What really gets me is the kind of articles that get the most votes. For example, I worked on and off for a couple months on my latest article, and as far as I know, the only votes came from my two coworkers.
Conversely, I spent probably less than four hours writing the code and article for Stop Writing Switch and If-Else Statements![^] and it won first prize! And I thought people would hate it because of the bizarre syntax and performance hit that occurs simply to avoid if-else statements!
To quote Kirk in my favorite Star Trek movie: "I have never understood Klingons my audience, and I probably never will."
If I had to offer a guess, I'd say it's how relatable the article is. Anyone that understands C# can relate to the switch/if-else article while the newest article is more niche. Good article though, even if personally I suddenly develop narcolepsy when it comes to most JS libraries that are replacements for a dozen existing libraries. With that said, I wholeheartedly agree with the introduction points and #6 under pros. More libraries should at least attempt that where possible.
Yes, I agree. The problem with the way I write is that I don't necessarily want to write about relatable stuff because most of the time its either boring or many other people have already written about it. Personally I'm more interested in writing the "there be dragons here" falling off the edge of the known world articles.
I wouldn't dwell on it - whats the saying, 'haters gonna hate' (yeah, I deserve 'ok boomer' for that) - but how many of these turds have the guts to stand up and produce meaningful content ? they are less than pimples on a maggot's butt, so don't give em the satisfaction
Downvoting all those braceless single line if-statements
Seriously though, those people suck.
What bothered me in the past, wrote an article, got all 5's and then someone voted a 4.
HOW DARE THEY MESS UP MY PERFECT SCORE!!!
But then again, some people just don't vote 5 ever because nothing is perfect.
The 1's are ultimately left out of your score because they differ too much from the other scores I think, so
I recently wrote a project to demonstrate a message passing and thread pooling paradigm "in the raw" (coded manually, not using the .NET task or thread pool infrastructure) so that folks could see all the moving parts.
I wanted to make something more production ready, and to show how to do the same thing using the built in Task framework and thread pool in .NET
So I start porting the app over, and one of the things it allows you to do is get/set the number of waiting threads in the pool. Well I did that with the built in thread pool and got 2047 waiting threads back.
Even the docs suggest that's obscene:
Use caution when changing the maximum number of threads in the thread pool. While your code might benefit, the changes might have an adverse effect on code libraries you use.
Setting the thread pool size too large can cause performance problems. If too many threads are executing at the same time, the task switching overhead becomes a significant factor.
Now I know that they're all sleeping, but seriously, how many kernel wait handles does a process really need to allocate?
And it makes me wonder how reliant the Task framework really is on spawning actions on other threads. I have to believe it's performance tuned, but why so high? Do they really think we need that many waiting threads?
I expect more like a few at most for most applications, and a well written app shouldn't have more CPU bound operations than there are CPU cores (or hardware threads) when possible, so why so many?
Sometimes I miss working at microsoft. I knew which team to email with questions like this.
Thanks @JSOP for pointing me to SmartThreadPool. Even Stephen Toub wrote his own implementation of a thread pool so i think maybe I'll go that route, unless the thread i just tugged - a custom TaskScheduler can let me have my cake and eat it too.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!