He made the following statement during presentation: "Hopefully this time we got them right!"
People make mistakes - why not let them fix the mistakes.
Because the CS field as a whole sounds like a crack addict and "let's invent a new bytecode and a new language" sounds like the payload for inhalation.
This churn - and it is churn - limits the expertise of anyone working in the industry. You cannot become very good with a given language and platform, because it is defined out of use too quickly.
C++ has an extremely rich ecosystem of best practices, books, articles, and libraries. It's been in use for >20 years and has only improved. I'm not saying that it should be used for everything, but C++ *has* improved dramatically over the years and so have practices in using it.
The C++ of 1998 - proprietary and expensive Rogue Wave C++ libraries, MFC, and inconsistent use in industry - was crap and I hated using it then. Since then, widespread practices such as the use of "smart pointers" and container classes and STL have homogenized how C++ is applied. The C++ of 2010 is a quantum leap over the C++ of the 90s.
If C++ had been obsoleted in 1998 you would not have seen this improvement.
I recall in 1995 that Java was heralded as a millennial advancement. At the time my instincts were that it was proprietary so I wondered just how far it could go. Now it is yesterday's trash. I know it's legally tied up by a shitty company (Oracle) but the fact remains, an argument for "new language" can always be made.
Summary - I think the impact of heralding new computer languages has been trivialized. I don't like forced obsolescence because it marginalizes the human capital, namely the skills of those who are invested in current tools. Ultimately this sort of thing keeps this industry immature and "de-skilled."
New computer languages are proposed and rolled out these days the way major libraries used to be a couple of decades ago.