It's like me writing a report to my client on "should you use an HTTP API", ending up with "probably yes but it depends so check with you local web dev" and sourcing O'Reilly books. It's political correct bullshit: as the expert, it's my job to not only give a strong actionable conclusion, but to justify the hell out of it.
Have you read the list of possible side effects of the drug ?
https://www.drugs.com/sfx/malarone-side-effects.html
This is a very active product.
If you advice somebody to take it PREVENTIVELY when you are healthy, not even mentioning on a long period of time, you better have a really compelling case.
Not just "meh, yeah do it".
Isn't the point of orgs like the CDC that individual citizens, who aren't experienced in the field, don't have to attempt to analyse the data for themselves; experienced people with expertise who are demonstrably not biased by commercial interests, should be giving you a simple result that anyone with a 11+ yo reading comprehension can follow and know they're doing what most experts would recommend.
If the advice differs from other country's health organisations, or from the WHO's then they should say why.
Imagine if someone who read a few articles about programming started to debate with you about the relative merits of direct SQL use vs. ORM--he might say "ORM c'est de la merde." I'm sure you would explain there are tradeoffs, it depends what you are trying to accomplish, etc. Experts in a field establish guidelines for a reason.
https://wwwnc.cdc.gov/travel/yellowbook/2018/advising-travel...