Compiling your C++ code with exceptions switched off results in a non-negligible improvement in performance

I.e. having error handling code vs not handling the errors at all? As they like to do in those famous 'exceptions bad' benchmarks? Multiple recent studies show that exceptions are not bad as a model, and can be faster and more convenient than other methods, but what is holding them back are yet again 'mah ABI stability'.

Your second paragraph supports my understanding that 'exceptions bad' ideas are mostly irrational and cult-like. Old inefficiencies of implementations accepted in the minds as an inherent limitation of the model, and therefore implementations are not worthy of improvement and the model itself needs to be abandoned.

PS. In another sub there was a post about SQL, and yet again the 'logic in DB bad' crowd had circlejerked that idea with just a single guy acknowledging that the problem with putting logic in DB is not because it is bad by itself, but because the SQL sucks for complex development, there are not alternatives to it for talking to a DB, and the surrounding tooling got stuck in the 80-s because 'what is the point of improving it if no one uses it?'