|
W∴ Balboos, GHB wrote: risk of vaccination vs. risk of none. Hard to know for sure. There was just an article a couple of weeks ago that 100% of people in someplace in the UK that had recently gotten COVID were vaccinated. I don't remember the details.
|
|
|
|
|
SeeSharp2 wrote: There was just an article a couple of weeks ago that 100% One of our current era's greatest problems - "you read it somewhere" -
That could be very interesting, or made up, or true-ish, leaving out important facts that can cast an entirely different light on the report. Just the way things have become.
But that aside, I can point out that in the US (Mainly Pizer, then Moderna and J&J), the vast majority of cases in the what I'd call "anti-vax" states are the unvaccinated and, when you move on to hospitalization, it's all but exclusively the unvaccinated.
The real point (to me) has always been not 100% protection from catching it but essentially 100% protection from getting very sick from it. That's where I put my money.
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
W∴ Balboos, GHB wrote: - "you read it somewhere"
Too true. But that's essentially where all of our "knowledge" comes from.
|
|
|
|
|
In the U.S. almost 100% ofthe people dying, or severly affected by Covid, including the 5 variant, are those not vaccinated. ABC Nightly News.
Also 99% of those severly affected, to a person, said they wished they'd been vaccinated.
I don't know what's going on in the UK, but, short of a bad batch of the vacine, or placebo innoculations, I have trouble believing that.
|
|
|
|
|
That's hardly surprising, in fact it's inevitable. In the extreme case, 100% of the population will be vaccinated, and in some localities, it's already close to that now. So of those who fall into that "5%" (for whom vaccination does not prevent covid), 100% of them will have been vaccinated. But as a result of vaccination, the number of people who got Covid is 1/20th what it would have been without.
|
|
|
|
|
|
Plus, the use of "placebo parachutes" is going to be ... um ... unpopular
"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!
|
|
|
|
|
Liked the way you dropped that one in!
Repo Man
|
|
|
|
|
Exactly. No one way of testing (or developing or documenting) "things" is appropriate for all types of things.
|
|
|
|
|
You got that right! Those government goon got us!
I am going to stop using parachutes effective immediately!!
(I think I'll be fine, I never jumped out of a perfectly working plane yet!)
|
|
|
|
|
SPCA is still protesting the use of animals in parachute trials.
I know I read that somewhere.
If I recollect it was write above the POST button.
|
|
|
|
|
I have to make a little application, read an Excel spreadsheet, create some PDF files and send some emails.
Thought I'd check out the new WinForms in .NET Core.
I thought Microsoft released a stable version, but constant crashes, weird behavior and simply unsupported basic functionality determined that was a lie...
Visual Studio just crashed so hard I had kill all instances in the task manager because the default "the application crashed you may close it" dialog crashed as well, and VS crashed because it hit a breakpoint...
Third crash to desktop in about two hours time, not counting the times I had to restart to fix some off behavior
|
|
|
|
|
Do you have to insult us?!
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
perhaps some clue as to what is really happening during this crash, can be found in your OS application event logs. I am sure it is not entirely Microsoft Visual Studio's fault.
|
|
|
|
|
Nope. For someone (as in moi) that was admittedly anti-web a few years ago, I pretty much write everything as a web app nowadays, even small utilities. Crazy.
Sander Rossel wrote: Thought I'd check out the new WinForms in .NET Core. You're brave
|
|
|
|
|
This is a serious question. If you make small utilities as web apps, doesn't that mean you have to have access to a web server? I do a lot of WinForms tools, and it seems that getting a web service installed on a customer's server is a hurdle I've never tried to jump for small things. I may be missing something important though.
|
|
|
|
|
You're right, although once you have access to a web server and deploy automatically using CI/CD, adding an extra service is not so difficult anymore.
If it's a small utility for your own purposes, I guess you could run it directly from Visual Studio (which is what I do with some stuff).
|
|
|
|
|
Rich Shealer wrote: If you make small utilities as web apps, doesn't that mean you have to have access to a web server?
Sorry for the delayed response.
Our company manages our own servers (well, AWS hosted) for the product line, including development servers, etc., so I primarily install these utilities on the development server domain which we have access to internally or through a VPN. Also I probably should have clarified that these are utilities we use in-house for monitoring and managing rather than utilities we expose to our customers. If it's a utility that needs to be exposed to our customer, it gets folded into the customer-facing product somewhere under configuration / maintenance.
And if it's a really one-off thing that simply makes my life easier, I just host it locally under IIS and put the code in a company repo somewhere so that others have access to it if they want.
|
|
|
|
|
I made a small program in it recently (same thought process as you, figured I'd check it out).
Aside from some weird issues with visual studio (buttons not being there, shortcuts not working (F5 for some reason doesn't work)) I haven't had any major issues or crashes.
But I haven't done anything as "advanced" as you with it though, although I have a "export to pdf" feature in mind, I haven't had the time to implement it.
For the moment it's mostly reading / writing to a json file and downloading a image from the web. (so nothing advanced)
I'm also using the free visual studio one for that program (the community one) so I just blamed the weird stuff on that, but ...
Tom
|
|
|
|
|
I still haven't made the jump to .NET Core, and I've been telling myself I won't do that until WinForms is there and ready and usable.
Your post tells me I made the right decision.
|
|
|
|
|
Sander Rossel wrote: I thought Microsoft released a stable version, The MS teams that are throwing out preview this and preview that ... Web this and WebApp that, Maui this and Xamarin that ...
imho, none of the stuff is usable, or reliable. i think there's some kind of "publish or perish" culture-thing at play ... sacrifice of quality for flag-hoisting.
«The mind is not a vessel to be filled but a fire to be kindled» Plutarch
|
|
|
|
|
Use the WinAPI and the old common controls.
It be fast and predictive.
Bastard Programmer from Hell
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Hi Eddie, for you and i, and, other WinForm "veterans:" i wonder if they are "common" because we have long ago learned their quirks, and work-arounds for their limits.
Speaking from my experience teaching bright, mature, students C# and WinForm UI skills, i observe there is a steep initial learning curve. Watching students wrestle with the DataGridView reminds me how i've forgotten how overwhelming its ginormous number pf properties were to me.
i find little consistency in how the classic controls evolved from their origins in COM into VB%, and then C# WinForms.
When WPF came along, i had high hopes for its controls, but, i just could not get into it.
On the upside (?) ... the deficit in native controls imho created a commercial opportunity for 3rd. parties to thrive. My favorite WinForms 3rd. party controls remain the ones from Lidor Systems, the IntegralUI Suite, which i purchased with source code: they are visually beautiful and performant ... of course, i can't compare them with the much more expensive suites from Telerik, and DevXpress, etc., that i have never tried
«The mind is not a vessel to be filled but a fire to be kindled» Plutarch
|
|
|
|
|
BillWoodruff wrote: Hi Eddie, for you and i, and, other WinForm "veterans:" i wonder if they are "common" because we have long ago learned their quirks, and work-arounds for their limits. That's a veteran? No, the first common controls were designed to be recoginizable (recognizabilty), to implement features for impaired (accessability).
The common controls were a revolution; after that, you nog longer needed manuals, because you could guess what a control asks you, and you could clearly see where it was.
They ARE still superiour, because a team designed them, instead of sales. Everyone on the planet recognizes COMCTL32.DLL. It's free, and even people with bad eye sight can use it.
Why choose anything less evolved? And by "evolved" I mean those features been there before Win95. And you still looking for something "better", eh?
I worked with Telerik and DevXpress. Those surely not "common" controls.
Bastard Programmer from Hell
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
I spent a whooping 10 minute with WinForm on .NET 5...
It all seem to work fine....
That was just out of curiosity, using WPF.
As a side note, if by .NET Core you mean .NETCore 3.1 or less, that might be the reason why. It was not yet fully supported by then. Try again with .NET 5!
|
|
|
|
|