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.
Death rates vary by country - in fact, the counting method here, in the US, has actually varied by state - especially those who chose to ignore it all as a hoax. They're paying for being stupid even as we speak - or should I say, the citizens of those states are paying . . . you can be pretty sure the "management" discretely took precautions. To them, keeping business' open was (and still is) more important than saving lives. Besides, you get the symptoms AFTER you've paid your restaurant or gym/spa bill.
The figure I quote was from the OP - which can vary. The multiplier is from a CDC statistic on mortality vs. age group, setting the mid-to-late-20's as "1" . The death rate increases as the hospitals fill.
As a devil's advocate point, remember that many go asymptomatic and don't get tested - escaping the count and otherwise not lowering the rates. But that's not the point. US death toll, now, is around 400,000 - > 1 in 1000 . Daily death tolls haven't been a "low" as yours since November. Morgues are overflowing into refrigerated truck containers.
This is not the flu - this is a killer (and, as I alluded to and you described in some detail, a crippler, as well). We live in an age where morons want to believe it's a conspiracy - a hoax - perhaps a plot by the Illuminati. So they won't recognize it and take the vaccine. I have a solution to someone who won't take the vaccine: "who's next in line . . . .". I see no reason to talk someone into accepting something such as the vaccine that is so coveted and yet in short supply.
Perhaps, now that the vaccine is available, victimhood will shift ever more towards the fools and fanatics - and so their relative proportion in the population will decrease. When it's over, perhaps it will end up Darwinian in overall effect. The reality, however, is that there's immense sadness as the victims, to start with, were primarily blameless. The party goers? For them I've fewer tears to shed. It's like a biological version of drunk driving. Endangering themselves and others around them "because they have rights".
The precise number/mortality rate isn't important. It's that a deadly disease was politicized. Worse, I perceive (a risk of being political) that the current administration here lied about the "backup" vaccines they have in store and is reversing a ban on air traffic from Brazil and South Africa (even worse variant than UK variant) - to exacerbate the problem for the administrations successors.
Perhaps, now that the vaccine is available, victimhood will shift ever more towards the fools and fanatics - and so their relative proportion in the population will decrease. When it's over, perhaps it will end up Darwinian in overall effect.
we won't be so lucky...
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.
My last use of carbon paper was several decades ago: I used it as a detector for when I got the preliminary alignment of "my" CO2-TEA laser going. It was even more sensitive than a fluorescent (heat sensitive) phosphor that the professor bought for the purpose. Also, using the fluorescent screen had a secondary drawback: anything much about the bare minimum laser output smoked the sucker - literally. When that happened to the carbon paper, you just moved to another spot and did your best to avoid fires. Sort of worked, years later, with a flash lamp pumped dye laser.
I'd probably seek some out, again, if I were bringing up lasers again.
I have about 1000 sheets of fanfold carbon in my office. When a trainee programmer in the 80s I tested a program that printed to 3-part line-printer. Foolishly (I lived and learnt) the first run was with the correct stationery. It had an endless loop. The operator phoned me up when the first box of stationery was all used up (only printed one line per page) checking if I really needed it, and how many boxes it would take. He made me come down to the machine room and collect it. Seemed an embarrassing waste to put it in the skip, so I took it home as "I'd need carbon paper sometime".
So we've built a system that uses Azure, it's a function that validates a payload and pushes it onto a queue, and then another function pulls it off to process it. It's integration, keeping two systems in sync
Worked fine until the client decided to push in 2000 records at once. We find that HTTP functions blow up if they get too many calls. At one point they were sending 20, waiting 30 seconds, sending more and that still blew up.
We've been chasing this for over a month. There's Azure doco on this being limiting code that you can turn off. You cannot. The doco is all over the place. We found it doesn't happen to C# script BUT C# script won't work with queues with sessions.
Today we get one of my co workers to code review it all. He says it all looks good then, off the cuff, says, why does your DI code use injecttransient. Because we're injecting a few lightweight classes and I didn't trust the idea of a singleton across Azure servers being better.
So I make them all singletons, and now the code works. No documentation anywhere that I can find on why that would be.
There are tons of undocumented behaviors in Azure - it is an environment developed in production...
For instance (from my personal experience) a Linux based app service is actually sits behind an IIS wrapper, where that wrapper always 'talks' to the Linux instance in HTTP, which actually makes it unusable for like 90% of the scenarios in today world, where HTTPS is a minimum requirement and checked by most...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
Feel free to ignore this because it's just a wild stab in the dark (and it's obvious once one knows), but are you somehow injecting an HttpClient using transient ?... because HttpClient is (as I know due to (cough) experience) "once per app" and exhibits interesting behaviour if it's continually 'new'd ... see first comment line in the c# example (link below) and text in the in the Remarks section...