Codecs designed for conversation are limited in how much they can compress because they can't use as much correlation over a long period - to avoid long latencies. The Intelligence agencies have probably designed their own compression algorithm focussed on offline storage. My guess at the reasons that low-bitrate codecs are export controlled are 1) submarines and 2) covert channels.

Feel free to pay to have that done. the algorithmic versions (PESQ, POLQA) are proprietary, and doing it with real people is also pretty expensive.

We don't need the google translate version, there is an official one: http://www.spiegel.de/international/zeitgeist/george-church-explains-how-dna-will-be-construction-material-of-the-future-a-877634.html

Yes, EXCEPT it's not just the servers' IPv6 connectivity that has to be reliable - the clients has to as well.

Knuth says no to email. You think that means his views should be discounted as well?

Strachey was also the lead programmer behind the programming language CPL, the great-grandfather of C (via BCPL and B). CPL was too ambitious and was never completely implemented - it tried to do everything; a bit like Perl 6 really.

The overview paper:http://comjnl.oxfordjournals.org/cgi/content/abstract/6/2/134 is quite interesting; sadly it is now behind a pay-wall. There are some features of the language, such as type inference, which have not become common until recently. It also has some obvious poor decisions with hindsight - the same character starts and ends blocks; all lower case letters are single-character variable names; multiple-character variable names must be capitalised (this is done to allow implicit multiplication, ie, xyz=x*y*z). I suspect it could be implemented without huge difficulty with modern tools. Unfortunately, the full definition was never published, and only exists in a few copies of 'The CPL Working papers' archived in university libraries. Perhaps one day google will scan it.