Good thing reality seems to disagree with Lisp Curse. Wonder why more people don't point out the much larger scale of the problem in C++ (yes, they do point it

Good thing reality seems to disagree with Lisp Curse. Wonder why more people don't point out the much larger scale of the problem in C++ (yes, they do point it out, but where are the capitalics about "The C++ Curse"?) As for #5 - that's mostly a problem with Scheme, where implementation specific issues abound, but most other languages in the family don't have multiple differing quality implementations. In fact, a common argument for Common Lisp instead of Python, is that unlike Python Common Lisp has a standard and implementations adhere to it - and the rest is handled by common portable libraries. One doesn't have to deal with spec that amounts to "what's the actual emergent behaviour of PyEval_FrameEx".