I don't deny global warming, but what is being done about it is crazy.

Personally I think it's what's not being done about it that's crazy.

Back on topic: I agree that a rethink of personal transportation is required. I think it is more important to rethink the things that cause us to need or want cars. Living in a different town from one's workplace is rarely if ever required. The centralisation of services that widespread car ownership has permitted (think malls or retail parks) is amongst the myriad of reasons we feel we need cars. Research like this is useful and worth while, but as others have pointed out what's really needed is a more fundamental rethink. I'd like to see us reordering our societies and lives in such a way that we don't need cars.

Agreed. In a dog-eat-dog world you eventually end up with one very fat dog.

http://www.tartanhen.co.uk/ebooks/ygg/title.htm

...For correcting my correction. I knew I should have paid more attention in Klingon class.

I'm not a Trekkie, although I am a bit of a sci-fi buff. The Klingon homeworld is called Qo'noS. This is Slashdot, if we can't get this stuff right here then something is very wrong.

It's more like spacequake. I've played both and TBH I much prefer Vendetta. Even is too much point-and-click for me. YMMV.

I want to be recycled.

Out of interest do you expect code to compile first time?

I'm always suspicious if this happens, but it's probably because I don't do much coding in my job - when I do code it tends to be scripts to quickly test something/process data (or some embedded code for a micro controller) - as such I always tend to be using different compilers (esp embedded ones which always seem to have their own set of non standard stuff), languages (python then C++ etc).

As a result I'm always making some sort of grammar mistake (i.e commenting out C++ with # instead of //, missing the odd semi-colon, pressing tab instead of spaces (or not setting up the text editor to handle this correctly) or forgetting the correct way to refer to a member function via a pointer etc..)

It could just be that I'm used to compiling being the fastest way to catch this kind of problem in most cases.