But it would be iOS only, because 12-step programs are religious in nature.

A combination of encryption and steganography will soon follow. ;-)

That's what Dynetics is trying with the F-1B project... With 8 MN of liftoff thrusts, despite the other projects in the works (the Falcons, Vulcan, the mythical Blue Origin launcher), it could still make for an interesting single-stick launcher.

Neither Dachau nor Sachsenhausen were extermination camps.

When you're high enough, it is.

Conservatism happened.

But what's the productivity? How much more environmental impact does it actually generate if you replace a tonne of vegetable fat with a tonne of animal fat? If it's problematic enough with food, I can't see how oils could have it different.

Android, currently. ;-p

You're assuming that salespeople can't be automated away. Also, that there will be jobs in the future. A plausible bet but still somewhat risky.

You started with a laundry list, I didn't. When it comes to that, CL is hard to beat. "Playgrounds"? What about reshaping the whole program on the heap while it's running, almost without limitations? Including persistent object databases if you have those (one might argue that without the ability to do that, transparently integrated object databases are quite difficult to pull off). You can implement any kind of workspaces or scratchpads or playgrounds (or what's the nom du jour for that ancient feature, dating back to Smalltalk-80, if I'm not mistaken) based on this solid foundation. But not the other way around. Many people don't need any of that, though. Certainly it's not the focus for the above mentioned server use of Go.

Then why isn't your build system written in the same language? Presumably it's a smaller software artifact of its own so bootstrapping it shouldn't be difficult even in the most pessimistic case.

There's also Maxima (formerly Macsyma) and REDUCE, both of which started in late 1960s or something like that.

It's shitty to write in directly, but a reasonable back end for compilers, though. Even more so with the future tail call elimination.

Go is a replacement of C for servers. So quite obviously some of the things aren't going to be there, since it's generally somewhat more conservative. More so as it's geared towards people writing their own language processing tools for heavy lifting in really large projects (admittedly, probably not something for the average phone app developer) which gets obviously easier if the language is simpler. That could make it a pretty good choice especially if you want to share code between a server and a client AND you're already settled on using it on the server side. Anyway, a laundry list of features ("half-features" for some of those you named to boot) is hardly an argument. If I want the ultimate rich ultra-flexible language, I already know where to find it.

Taxadermy being skinning people alive as an IRS officer? Sounds fun, actually...