I don't think it's about "going back to basics". I think that companies and other organizations are just fed up with what they get when they don't deal with C++ and C++ developers.
If they choose Java, they often get a slow, bloated, extremely over-
"engineered" system. Although simplicity is often given as one of the reasons for using Java over C++, the complexity of these Java-based systems often far exceeds what we see from even large C++ systems.
If they choose Ruby, they are almost guaranteed scalability problems if the software is to be used by a large number of people. The effort and cost needed to scale a poorly-performing Ruby on Rails web application, for example, can exceed that of using a language like C++ in the first place.
When it comes to other languages, it may be difficult to find talented developers. This can pose big problems when it comes to maintaining software systems written in a more obscure language.
C++ has time and time again shown itself to be a safe bet. There is a large, experienced and global developer community. There are ample resources and tools available. It is extremely well proven, even for absolutely massive systems. Systems developed using it usually perform quite well without much effort.
It offers a better set of trade-offs than other languages. While it may take longer to develop a system using C++, there is often at least equal, if not much greater, time saving in other respects. Avoiding scalability and portability problems alone can offer massive savings.
With regard to java, a lot of the complexity is in ancillary systems rather than language or the libraries themselves. You may not like Maven, for example, but what's the c++ equivalent? Autotools? I think not. Any cross platform c++ project immediately falls over the build system problem before you write a line of code, and most of the time we choose a non-native, underperforming solution (eg. MinGW on Windows) - anything for a quiet life. Honestly, Java would be a better answer.
"When it comes to other languages, it may be difficult to find talented developers" I disagree. Actually it is harder to find good C++ devs than to find good C# or Java devs in my region. There are lots of poor C++ devs out there, who learned only the language taught at the university (C / C++) and who really can't code.
If they choose Java, they often get a slow, bloated, extremely over- "engineered" system. Although simplicity is often given as one of the reasons for using Java over C++, the complexity of these Java-based systems often far exceeds what we see from even large C++ systems.
If they choose Ruby, they are almost guaranteed scalability problems if the software is to be used by a large number of people. The effort and cost needed to scale a poorly-performing Ruby on Rails web application, for example, can exceed that of using a language like C++ in the first place.
When it comes to other languages, it may be difficult to find talented developers. This can pose big problems when it comes to maintaining software systems written in a more obscure language.
C++ has time and time again shown itself to be a safe bet. There is a large, experienced and global developer community. There are ample resources and tools available. It is extremely well proven, even for absolutely massive systems. Systems developed using it usually perform quite well without much effort.
It offers a better set of trade-offs than other languages. While it may take longer to develop a system using C++, there is often at least equal, if not much greater, time saving in other respects. Avoiding scalability and portability problems alone can offer massive savings.