Except the data doesnt back up that assertion. Golf course employees and golfers have no higher rates of than the public at large. So what gives?
If the very people who spend most of their waking lives on the grounds and among those fertilizers and pesticides do not have any great instance, maybe just maybe its something else. Like the gallons of unregulated chemicals that are in those tract houses that were all built around the same time...
one example is the drywall was used extensively in the 90's. Its makeup banned in the country of origin, China but its product was used all throughout the US for decades.
The correlation seems to point to usage ground water that is contaminated with pesticides. So people living close to the golf courses have higher Parkinson risk.
Probably golfers and employees less so.
Personally, I’ve been using a wrapper around `collections.namedtuple` as an underlying data structure to create frozen dictionaries when I’ve needed something like that for a project.
That works if you're dealing with a known set of keys (i.e. what most statically-typed languages would call a struct). It falls down if you need something where the keys are unknowable until runtime, like a lookup table.
I do like dataclasses, though. I find them sneaking into my code more and more as time goes on. Having a declared set of properties is really useful, and it doesn't hurt either that they're syntactically nicer to use.
Just like this scheme, it's not very economically efficient.
Carnot efficiency is proportional to the temperature ratio between the hot end and the cold end in degrees Kelvin. If both temperatures are in the 200's, then efficiency will be low.
OTEC does provide lots of potable water though, so that's one advantage.
reply