I feel like we see the same things with languages as we had with version control. For a long time, you had only CVS, then you had (too) many options to choose from: monotone, darcs, mercurial, git, and I certainly forgot some.
Now, we see new languages appear (and get some exposure) at a frightening pace: Rust, Go for system programming, and on the JVM: XTend, Ceylon, Kotlin, Clojure, Scala, Groovy, etc
It's great to see things move, but when you have so many option, it can be hard to make a choice. I expect some of these to take the lead, like git seems to be doing in the DVCS space.
You arranged a bunch of companies and programming languages which were designed by those companies (or with their support) and said that the motivation for designing those languages was "control". The fact the some of these examples were indeed (at least partially) motivated by "control" doesn't prove that all other examples fall into the same category.
Mozilla wants Rust to have control over their programming language?
Neither Facebook nor Amazon are developer's companies. They will do very well with whatever technology they used. Amazon will run any program written in any language on their elastic cloud. Facebook's apps can be written in any language, too.
Now, we see new languages appear (and get some exposure) at a frightening pace: Rust, Go for system programming, and on the JVM: XTend, Ceylon, Kotlin, Clojure, Scala, Groovy, etc
It's great to see things move, but when you have so many option, it can be hard to make a choice. I expect some of these to take the lead, like git seems to be doing in the DVCS space.