The entire first half of the article is dedicated to why "C++ with exceptions" is not acceptable for software that strives to have zero undefined behavior. Your proposed "better title" doesn't make sense given the article content.
He doesn't really make a case for not using exceptions though. He misuses the term "undefined behaviour", doesn't discuss RAII and doesn't give any concrete examples.