[Gravityloss]

The concept of laws were invented thousands of years ago to prevent just these tragedies. So we already have a solution. Now we only need to create such laws that pollution is greatly diminished.

This will naturally lead to creation of lots of ecological niches for new startups, that will find the most efficient means to achieve these reductions. Naturally government funded long term research will also play a part in finding good solutions.

The end customer will naturally pay for these changes. For example, it is cheaper to run transport ships with residue heavy fuel oil, the use of which has been banned almost everywhere else already. If we want to prevent that, we make laws that make it illegal. Then the ships will use some other, naturally more expensive fuel. The transport costs will go up and whatever you buy that was imported costs more, or whatever you export potentially pays less.

[ble]

Laws are better at protecting individual rights and maintaining public order than protecting future generations from the unintended consequences of present and recent economic history.

[Gravityloss]

There are quite a lot of anti-pollution and other laws that work very well. Why wouldn't they? You have to protect the society as well. If someone does damage to your property, I assume you'd think it's ok to protect you against that? What if the property is owned by the state? Or is an important natural resource that is not owned by anyone, but depended on by millions, or even billions?

Also, where do the laws come from? Many environmental laws enacted by nations are influenced by international treaties - this is required because many environmental problems don't respect borders. Take for example waste water cleaning and the Baltic Sea.

It is hard to create such treaties. But it has been done and can be done in the future.

[dredmorbius]

That's where custom, tradition, and taboo come to the fore. They're somewhat stronger in terms of social signalling over time than mere laws.

Jared Diamond's Collapse explores this, both in positive aspects (Japan and several successful adaptations in Pacific Island and Borneo populations), as well as negative ones (Greenlander's insistence on raising cattle and not adopting Inuit practices).

[ble]

I liked Collapse, but I really liked "The Collapse of Complex Societies." Written by an archaeologist, addresses many other scholars' theories of collapse, and provides an excellent economics / complexity argument.

http://www.amazon.com/Collapse-Complex-Societies-Studies-Arc...

(not an affiliate link)

Also, the idea of "diminishing marginal returns on added complexity" suggests a lot about why maintenance, extension, and management of software systems becomes harder over time.

[dredmorbius]

Joseph Tainter. Very familiar with it, and it's excellent.

You'll find that Diamond cites Tainter and draws much from his model of collapse.

The funny thing is that I'd started evolving a theory of systems complexity before running across Tainter. It runs basically like this:

⚫ Proof of concept. Works for the creator.

⚫ Refinement: Incremental improvement of concept in function, reliability, efficiency, and utility.

⚫ Embellishment: Layering complexity on top of an initial design. Though initially well intentioned, the end result is fragility, impediments to usability, and eventually, rot. A baroque era.

⚫ Recaptitulation or replacement: An overly complex design may find itself refined back to a more functional one (e.g.: the car tailfin era recaptitulated into today's econo-box and performance sedan market, though SUVs perpetuate the meme of ostentatious nonfunctional embellishment). Or it may find itself replaced entirely by a more appropriate technology, as may be happening now with PCs being supplanted by tablets and mobile devices offering much of the functionality required by users.

Posted to G+ here (and yes, that's before I encountered Tainter). The idea had actually been percolating for at least a year prior.

https://plus.google.com/104092656004159577193/posts/NFEFMZdk...

It's not specific to any particular technology, and I've seen examplars across a wide range of cases: software (utilities, GUI apps, Web design, OSes), cars, audio equipment, aircraft, architecture, etc.

I think that what Tainter has to say corresponds strongly with this, though his point is also that complexity is undertaken, when it is, because it adds value and/or capability.

He also notes that complexity generally isn't undertaken for its own sake -- that there's a resistance to it.

Another correspondence with this is noting that a great many technical tools (high level programming languages, IDEs, revision control systems, etc.) are all effectively means for coping with complexity and that in the IT world, people are constantly working at the complexity frontier -- the reason software still has bugs isn't because we're not getting better at it (though sometimes I wonder) but because when we do get better, we make ever more capable -- and complicated -- systems. With more failure modes and hence bugs.