One of the most important characteristics of the Kyoto Protocol is that it sets up a framework for countries to work together on global warming issues. The point is less what it proposes to do today (the cuts it asks for are a drop in the bucket compared to what is actually known to be necessary in the long run) than that it bring all parties to the table with a framework to work within. The protocol wasn't set in stone when the US refused to sign it. There was plenty of room for negotiation. As the largest CO2 emitter in the world (and the world's only superpower), the US had a great deal of sway over exactly what the Kyoto rules were. What we walked away from was the global discussion on how to address a massive global problem.
When you look at the probable damages predicted from more extreme weather events, and rising sea levels and then consider that renewable energy is the only viable long term energy solution for the entire world of consumers, it becomes clear that the economic arguments against moving to renewables is noting more than FUD.
Finally, any new industry that requires substantial infrastructure will inevitably create massive numbers of jobs. Investment in renewable energy will easily produce more jobs than comparable investments in oil, coal, or natural gas. See for example this PDF for an analysis of the jobs that renewables would create.
a lot of the ideas in the mircosoft paper reminded me of plan9, the research OS that was developed at Bell Labs by th likes of Rob Pike, Dave Presotto, Sean Dorward, Bob Flandrena, Ken Thompson, Howard Trickey, and Phil Winterbottom. I would imagine that anyone interested in concrete examples of some of the ideas (specifically aggressive abstraction and location-irrelevance) should take a look at plan 9 (and its sister OS, inferno). In addition to analogs to the features mentioned in the Microsoft article, plan 9 has other very nice features to boot. The most interesting to me is treating EVERYTHING like a file handle. Resources from other machines, processes, com ports: everything is all available as a part of one tree structure. You can treat the I/O of a com port like the input and output of a file. A device driver can be written in a shell script (in plain text). Check it out: http://plan9.bell-labs.com/plan9dist/.
Slashdot Mirror
One of the most important characteristics of the Kyoto Protocol is that it sets up a framework for countries to work together on global warming issues. The point is less what it proposes to do today (the cuts it asks for are a drop in the bucket compared to what is actually known to be necessary in the long run) than that it bring all parties to the table with a framework to work within. The protocol wasn't set in stone when the US refused to sign it. There was plenty of room for negotiation. As the largest CO2 emitter in the world (and the world's only superpower), the US had a great deal of sway over exactly what the Kyoto rules were. What we walked away from was the global discussion on how to address a massive global problem.
When you look at the probable damages predicted from more extreme weather events, and rising sea levels and then consider that renewable energy is the only viable long term energy solution for the entire world of consumers, it becomes clear that the economic arguments against moving to renewables is noting more than FUD.
Finally, any new industry that requires substantial infrastructure will inevitably create massive numbers of jobs. Investment in renewable energy will easily produce more jobs than comparable investments in oil, coal, or natural gas. See for example this PDF for an analysis of the jobs that renewables would create.
a lot of the ideas in the mircosoft paper reminded me of plan9, the research OS that was developed at Bell Labs by th likes of Rob Pike, Dave Presotto, Sean Dorward, Bob Flandrena, Ken Thompson, Howard Trickey, and Phil Winterbottom. I would imagine that anyone interested in concrete examples of some of the ideas (specifically aggressive abstraction and location-irrelevance) should take a look at plan 9 (and its sister OS, inferno). In addition to analogs to the features mentioned in the Microsoft article, plan 9 has other very nice features to boot. The most interesting to me is treating EVERYTHING like a file handle. Resources from other machines, processes, com ports: everything is all available as a part of one tree structure. You can treat the I/O of a com port like the input and output of a file. A device driver can be written in a shell script (in plain text). Check it out: http://plan9.bell-labs.com/plan9dist/.