>>1
None of those. Not Javascript, or Java, or Scala, or Haskell, or Python, or C++, or any of that nonsense either. Common Lisp and Scheme are dead too in terms of adoption, but in death they are reborn anew.
People who are focused mostly on web development and toy project development have proverbial horse blinders on and are for the most part incapable of seeing the future.
The future is not object-oriented.
It will be a combination of structured, procedural, functional, logic/declarative, data-oriented, and domain-oriented. Parallelism will be conquered as heterogeneous computing, task-orientation and grid-orientation parallelism go mainstream.
C and OpenCL will dominate the low-end. OpenCL is really just C99 with SIMD/SIMT vector intrinsics and an API for task/grid parallelism and heterogeneous-compute allowing you to run the same code on different CPU/GPU/FPGA/accelerator architectures attached to a common bus. The next major point release of OpenCL will add a common ISA or bytecode IR, making it easier for language developers to write their own DSLs or even general purpose languages that also target OpenCL.
I imagine we will probably see a statically compiled Clojure/Lisp-like language that targets the OpenCL stack in the future, as well as perhaps something based off of Go or Python with less object orientation and stupid concurrency models (or in Python's case, the complete absence of). The Go-like will probably become the most popular.
Any language that tries to solve concurrency with just actors, STM (software transactional memory), continuations, and coroutines will ultimately fail in adoption uptake as it won't be able to approach the raw scalability of task/grid orientation on immutable data structures and simple lock-free/wait-free concurrenct queues which is the OpenCL model.