C++ Creator Confident About Its Future 241
bonch writes "Bjarne Stroustrup is confident about the future of C++. He says there is a backlash against new languages like Java and C#, and that developers are returning to C++." From the article: "He claimed the main reason why people are not aware of this is because C++ doesn't have a 'propaganda campaign.' Sun Microsystems has touted the use of Java in the Mars Rover program, for example, but Stroustrup asserts that C++ was also used.
C++ has a long future... (Score:5, Informative)
I wrote an article about the economics of programming languages that talks about this and other issues that concern the adoption and lifecycle of languages, although be forewarned that the login system is a bit fiddly:
http://www.byte.com/documents/s=9553/byt111384524
To those who have not programmed in C++ enough... (Score:5, Informative)
plagiarism (Score:5, Informative)
Re:To those who have not programmed in C++ enough. (Score:4, Informative)
The simple flat file C program that everyone can debug is also a small program. OO really comes into it's own when you get over 20,000 lines of code. Then the kiss C style starts breaking down.
Not an extension (Score:4, Informative)
A trivial conversion exists between any ISO C90 program and ISO C++, but then again, we have FORTRAN-to-C translators and nobody thinks C is an extension of FORTRAN.
Stroustrup would also likely be a little uncomfortable with the appellation "creator". While he's certainly been one of the pivotal figures in C++, Stroustrup has always been quick to recognize the contributions of other people and the work of the ISO standardization committee.
Sometimes C++ programmers miss the point (Score:1, Informative)
C++ is faster than java / C#
C++ has better templates
There is so much C++ out there that no one should ever use another language, or they will be forced into reinventing the wheel
Using a "simpler" language like java means that you will hire crappy programmers. Don't do that - use C++ and hire really good programmers.
Having worked on Wall St. as a programmer for 15 years or so, I'm sorry to say to all the people who constantly make that argument that they are officially behind the times.
The real reason to use java?
Compilation times
Compilation times
Compilation times
When programmers are a major cost (believe me, at Wall St. firms, they are a huge cost compared with the cost of machines), you should optimize the amount of time they spend waiting for compiles. We have a C++ library that is around 250,000 lines of code, that compiles in around 2 hours (and this is after a lot of work to try to make the compilation as fast as possible). We also have a 1,200,000 line java library that compiles in around 3 minutes. Any way you play it, programmers still spend a lot of time in the write code / compile / test cycle. In fact, this is where they spend most of their time.
In terms of performance, that is largely a myth that is no longer true. We run pricing simulations in java (which is about as computationally intensive as it gets) and we are able to do so at the same speed is the equivalent C++ code. In fact, the java code is a bit faster now, as the tools for finding the bottlenecks are much faster.
The hiring market? This is largely moving towards java. Many schools are not teaching C++ any more.
The work problem? In java, you spend much more of your time working on the business problem, and much less time trying to figure out why GCC arcane error message on file X means that your template is out of whack in file Y. Or in C++, trying to locate the source of a core dump (getting java.lang.NullPointerException is SOO much better).
Now, mod me flame.
Re:While it would be nice... (Score:5, Informative)
Re:Nice troll. (Score:3, Informative)
zerg (Score:3, Informative)
Re:Sometimes C++ programmers miss the point (Score:2, Informative)
Perhaps you need to take a look at your build system.
If an incremental change to you program is triggering a massive recompilation of everything there may also be a problem in how include's are being handled or your make files. There are several well known techniques to reduce this.