Hydro surprises some people, but in the best case a dam starts outby destroying a large swath of habitat, then permanently disrupts fish migration and the ecosystems dependant on the waterway.
And then when you blow it up to appease the environmentalists, it destroys the ecosystem AGAIN.
So your logic is: These thing over here kill birds; therefore it doesn't matter that this other thing kills birds.
Existing Facility Type A Kills X birds. Proposed Facility Type B kills Y birds where Y < X. Facility Type B is proposed to replace Facility Type A.
Facility Type B is sh*tcanned because it kills greater than 0 birds. Existing Facility Type B continues normal operation, killing X birds.
easily solved....audible chirps, clicks, etc to scare the birds away? Or maybe a little metal eagle or hawk statue on the roof..
How about an almost blindingly intense light with increasingly uncomfortable hot temperatures the closer you get to it?
So really all we have to do is convince people they are good eating and then make no efforts to protect the invasive fish
Oh, I'm sure the treehuggers will come out of the woodwork to protect the poor Northern SnakeHead and the Zebra mussel.
Email's strength is that it is asynchronous.
That's the theory. In practice, people seem to treat it like instant messaging.
In my company, we have e-mails going out to customers with attachments that they use in order to post balances to medical claims. Because it is e-mail, the delivery is not guaranteed. Yet if they don't get one, it screws them all up. We have had to jump through fiery hoops checking the server logs and everything else to prove that it got out of the office, yet I keep saying that e-mail is not a guaranteed delivery mechanism. Just because it happens to be very reliable does not mean that it is 100% reliable. I can't seem to convince them to take delivery of these files by something geared for file transfer, like say File Transfer Protocol or something.
In every non-trivial program there is at least one bug.