While there are other languages. Many poeples that have used C ++ in the past are not just about to pick up winners from Java or C #. Linux is doing fine and good in its own way, but most of the computer market still belongs to the evil empire. Java is not the dominant language there, no matter how religious Zealots claim to be. In fact, in small business applications, VB is king. I think I saw one figure giving 58% of the internal development for GUIs. C # is gaining momentum, but I suspect that this is primarily from a younger crowd, which is less tuned there. You can argue until your blueness becomes the virtue of a new language with someone who has been using the language for 15 years, and they don't care. "Oh, that's great". and they turn back and keep typing their C ++.
Edit:
OS, C development possible C ++.
The tool and development of Langauge, C is possibly C ++.
Industrial control, C, C ++, Labview in somecases, FPGA development and NO fashionable languages.
The nested set of C, some C ++ and some necessary assemblies.
(The iPhone is a universal phone-enabled PC. For special purposes.)
PS3 C, C ++ and some build required.
XBox360 Some C #, mostly C ++ and some C, and assembly is required again.
GPU programming? This is not PHP for confidence in DAMN.
Programming in Windows C ++, C # and even some C fixed, VB.
Edit:
@Jeff L: A cult following many of these languages, I find irrational and disagreeable. I am starting to move away from anyone who steals poetry about ANY language; it's just mental. It is not a question that professionally selling applications are NOT written in Java for Window, it is a fact. Sorry, but it's true. This may be useful in the IT world, but not for Windows-packaged software. I am writing embedded software, and the “function” of the lack of pointers means that hacks that break the language are required to do any practical work there or on the OS and device drivers. There are times when you have to "fly without a network", and interpreting languages are developed SPECIFICALLY so that you do not.
And not to be too controversial, but the legacy code base is a difficult issue to get around. Although we are writing new code in C and C ++, I can’t even get PAY control to update old code written in Fortran or Ada in C or C ++, forget Java, which requires a completely new coding standard and loading procedure and documenting downloads that cost even more. And if the only software you write is the GPL and the freeware that pay for it, is the main concern. And in many cases, “if it does not break, do not fix it,” it does not even apply, “if it breaks, and no one sticks, we do not pay to fix it” - this is the choice of management.