C++11 introduces new problems. Programmers are expected to know how a lexical closure should capture variables from the enclosing scope -- should it be by reference, or by value? Programmers are also expected to know that when they capture by reference, sometimes they are really supposed to capture by value but with smart pointers (and of course, they are expected to know which kind of smart pointer they need). Instead of fixing the double exception fault, C++11 just punts on the issue and says that no exceptions are ever allowed to propagate out of a destructor (which is another way of saying, "destructors must never signal errors, even for things that are correctable like running out of disk space).

That Microsoft would recommend JavaScript or C++ is unsurprising, considering how much business those languages have generated for them and how many programmers who support the Windows ecosystem are only comfortable in one of those two languages.