- Joined
- 11/29/11
- Messages
- 59
- Points
- 18
As I mentioned before you are using a legacy system that it's already established and free of bugs. Then, that system is used to generate C++ code (maybe because that was what the originals developers knew very well or for whatever other reason). Those systems are hard to remove from the pipeline. I'm sure the generated code is proven and almost free of bugs so the tweaks are minimal. Why would anybody change that system to another language? The old saying "If ain't broken, don't fix it".
The only time a new language could be introduce is when new development comes to a shop. However, if the people in that shop already know C++ (and probably they are very good at it), they will rather use that language than any new one, perpetuating C++.
I can give you a clear example of a transition. My group have a risk engine calculator that takes care of calculates risk parameters based on our groups in-house factor models. That engine was written in C++. When my boss came to the company (he is mostly a Java person), he re-wrote the whole engine in Java without penalty in performance. This is one of those rare cases that a new language gets established but for that to happen, someone needs to shake the world.
Once I came across a similar topic when reading threads when you were talking about the huge cost implied when willing to switch to C#. You said that most of the companies are willing and in future it is inevitable to switch to .NET and new technologies but it will cost them a lot of money. But gradually you are expecting them to change C/C++/VB and kinda "old" languages in favor of new ones like C#/F#,etc.
Here I read (I think) powerful arguments why C++ is not easy to replace. I liked all of your posts and you really seem to be knowledgeable around this area and I enjoy your posts, so my question to you is what makes you feel C++ will eventually be (at least largely) replaced provided the cost remains cost in future too?
Thanks