About the two-generation language. C/c++,java/c

This is not what I wrote, I just see feel good, just paste the oh.
：
Do not think that this topic is sensational, but in the current situation, C + + is required to exit the stage or to say that it is necessary to upgrade.
I think that in the next year or two, as one of the criteria for programmer rating, C + + (whether MFC or BCB) will give way to three programming languages, 1.sun Java2.windows platform C#3.xml
Why, I think the biggest reason is that the current application is being passed from a stand-alone operating system to an internet-based platform.
We used to develop applications that relied on the platform's functional invocation, MFC,BCB. And now the hottest Internet programming is the last thing to care about is the invocation of a certain platform, such as Business-to-business e-business, that requires integration of different platforms, If I were a programmer, my most care was how to achieve business logic.
Rather than communication and management between the various platforms. So what we need most is a language unrelated to the various platform calls, which focus on the design of the program logic and not on the platform's invocation. And we are familiar with C + + but it is not designed for this (hehe this can not blame C + + Who knows what the internet is like in the 70 's? The original design of C/s was designed to design UNIX to produce a highly efficient and inefficient language between the Assembly and the high-level languages. He is more concerned with the physical structure of the system than any other advanced language, For example, it has always been a denigrating. Pointers are powerful in that they should involve the management of the system's physical memory. He can make a semi-transparent state between the programmer and the system. But this translucent state gives the pointer more instability.
There is no advantage to C + + in programming for the Internet. Cross-platform e-business software is most afraid of taking into account the difference between the various platforms of the system call, the most fear from time to time due to memory leaks and crash.c/c++ Advantage here has become a disadvantage. Even if you are developing a solution based on Windows DNA on a Windows platform
Use the most or VB do DCOM instead of VC ATL do DCOM, because of C + + although efficient but too easy
Error, if not very careful to free memory NT will soon be under-resourced.
Java is the first to see this, he used the JVM to achieve platform-independent memory recovery to achieve a stable and robust. But quite a few C + + programmers complain that Java is too slow. Indeed even the java2 speed is still a big problem. I used to be a C + + A staunch supporter fights with Java programmers in many forums. But I've come to realize that Java's speed problem is often a minor flaw in the face of an internet platform rather than a particular operating system. We can imagine that an E-commerce site would use the PC we have on hand to do the server, They are not Sun e1000 is IBM's risc6000. On this platform Java this speed problem is only a peice of cake. Programmers only need to focus on programming with business logic without having to worry about whether the array is out of bounds, Whether or not the object memory is freed does not need to be concerned about whether UNIX and Windows system calls are different.