Skip to content

Comment on Tonnes of iron dumped off B.C.'s coastparent

Comments

If you can bring in toads to eat a significant fraction of the beetles that are destroying the sugar cane crops, why wouldn't you do that?

(Because: http://en.wikipedia.org/wiki/Cane_toads_in_Australia . These are complex, poorly understood systems, and the results will almost certainly not be what you expected. This isn't engineering.)

Exactly. Algal blooms drastically change the composition of the water that they are in. Fresh water algal blooms from run-off are incredibly damaging for local ecosystems, producing chemicals toxic to local flora and fauna.

Done over a large enough area, it can change more than just the CO2 levels in the atmosphere.

Iron sulfate doesn't reproduce.

The point still stands - although you are in control of one variable in this equation ("iron sulfate doesn't reproduce"), it would still be impossible to predict the consequences.

Iron sulfate does indeed lack reproductive capability. But it attracts plankton, which is a wide category of organism - some plankton can reproduce.

So long as the end result of all these extra plankton is not worse than "climate change threatens human civilization", I think we'd have a net gain.

"We need to do something. This is something we can do. Therefore we need to do this."

It's a false dichotomy. There's probably a wide range of things we can do, and picking an option just because it happens to be there & feasible, regardless of evidence of merit, doesn't seem like a winning strategy.

Put another way, you could cut off your hand to treat an infected wound. It's "feasible." But is it anything remotely approaching the best way? Furthermore, what if it turns out that artificially seeding the ocean with plankton is approximately as disastrous for the health of the ocean?

Obviously I do not advocate doing something for which there is no evidence of benefit... We shouldn't do it because it is merely "something", we do it because we can demonstrate that it does more harm than good.

If there are demonstrable benefits, then "do the benefits outweigh the risks" is something that we must consider. To categorically strike out broad classes of solutions because something might go wrong, without even considering the severity of the possibility, is to advocate inaction.

Any solution to this particular problem is met with this nonsensical "something non-descript might go wrong, so we better sit on our asses instead" mentality. What we should be asking ourselves is "What solution has both the greatest good/bad ratio, and can be scaled enough to actually solve the problem". Things are going to go wrong; to stop exploring a possibility as soon as we learn that something could go wrong is naive and if universalized will lead to our downfall.

"do the benefits outweigh the risks'

But that's just it: we have no way to answer that question. We can't say if it's a good idea because we don't even know if it's even going to yield good results, let alone what cost those good results come at.

I agree that we won't hit on some perfect solution which has no trade-off. But making a decision without even knowing what trade-off you're making could actually make things worse! Imagine if this does approximately nothing substantial for climate change, yet it kills off a ton of species. Now we're on a planet with an destabilizing climate and a substantially more destabilized ecosystem.

High stakes cut both ways. You can win big by doing something bold just as you can lose even bigger or sooner. And having people unilaterally try out their pet theories seems like a recipe for disaster. They'll likely be long dead before the effects of their actions are realized anyway.

Neither do CFCs, CO2, nitrous oxides, sulfer oxides, carbon monoxide, radioactive iodine, arsenic, mercury, dioxins, BPA, or any of tens of thousands of other toxic and/or harmful compounds we've released into the biosphere over the years.

The attribute of non-replication doesn't equate to "safe for the environment".

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.