so in 10 years haskell maybe as fast a C/C++ program without parallelism, not exactly my definition of future proof.
This is where Haskell comes in. Haskell allows you to program in a way that makes parallelization relatively easy.
It seems like you want to advertise a tool, instead of actually considering the issues.
His argument is that scaling silicon to multiple cores is facing physical barriers. You're no longer getting more cycles, improved transistor density, and decreased power consumption simultaneously. Exponential scaling of cores will not result in exponential scaling of computational throughput because we're facing energy-related tradeoffs.
On a chip there is now lots of redundancy to ensure chip functions correctly. This gets worse as variation at smaller geometries increases. So over margining because no one wants another floating point bug.
Design effort and cost is a huge issue too. Margins at chip companies are shrinking - design automation license costs, large runtimes and much more difficult verification process from design to fab to test.
A new programming paradigm where there is a certain probability of error can be tolerated should go a long way in making the underlying hardware much more efficient.