Another fix could be to use Hyper with tokio-tls. Under the hood, that package uses Windows schannel, macOS SecureTransport, and a dynamically-linked openssl on everything else.
All properly configured applications should be running with least required db credentials, limiting what they can do. That Accenture was monitoring all administrative level queries against the db makes perfect sense in a locked down production environment.
Having it built in seems just as likely to be a "bad thing", since that version is "baked" in, there's no alternatives. That's why the extension approach by VS code is so surpreme. I'm sure JetBrains would love to have a similar ecosystem.
Angry users is not something you can opt out of. Malware reports are just another fact of life for many open source projects. I think the putty link (was posted elsewhere) is an awesome summary of the impossible fight you're asking developers off taking on.
Also, that's an insane comparison between AV reports and personal credit reports.
It's pretty common for programs compiled by "uncommon" compilers, and since the D compiler is selfhosted, it would fall into that category. AV software isn't magic, they probably just look for stack/calling/allocation patterns that don't look "right" meaning none of the major compilers generate such code, and it "might" be bad somehow.
I've a few flags from npm with Kaspersky, because there's so many packages that include some little binary, and since this is npm, it's often "unusual", like go.
The AV might not be even looking at patterns in the executable code.
We've had an issue where we accidentally ran the msys strip tool over binaries compiled with the MSVC compiler. A quarter of the scanners on virustotal went crazy and "detected" our program.
The same unstripped program was fine with them. And by "the same", I literally mean the same: virustotal showed that all sections in the "malicious" stripped executable had identical hashes to those in the clean unstripped executable. The only difference was some header bits that were irrelevant to the runtime behavior (I think it was the "linker version" field, and maybe some others).
CSS and HTML will usually afford a specific approach. Being a web developer is knowing what these approaches are, and to know when stuff might get "not nice". So when you see a graphic designer using multiline text blocks with elided text in their design layouts, you know to raise a red flag and get that removed.
Personally, I've not found collapsing margins a huge issue either way. It's just the way it is. There's 10 billion ways to add distance between two elements in the browser, so pick a solution and go with it.
It's a "oh shiny" thing from my point of view. People get bored with the old, and want to try the new Google/Netflix/Microsoft tech, irrespective of its suitability. Once the client/customer signs off on it, internally it becomes political.
Interestingly, the term "font" itself came from the fact that typefaces were cast.
"Font" originally described a size, weight, and face. It no longer includes a concept of size, because digital typesetting allows sizes to be changed so easily. What we refer to as a "font" today was originally referred to as a "typeface," that is, the general style of the lettering.
This explains too how sometimes you see a list of every combination of every "font" in a list and other times you see every font and can configure them.
Likely some confusion around this in the documentation and in programmers who implement these features.
WSL is a godsend for developers. Having easy access to openssl with minimal fuss is awesome for all those obscure cert operations that you need a couple of times a year. Cygwin and all that has always been rather crappy IMO, so I'd usually keep a linux vm handy for those kinds of things. Installation can be slow yeah, QT took forever to build. But it did work!
