That is what RAII stands for, but in practice good use of C++ RAII is all about explicitly separating interface, allocation, and ownership, such that you only p

That is what RAII stands for, but in practice good use of C++ RAII is all about explicitly separating interface, allocation, and ownership, such that you only pay for as much initialization as you need when you need it. This takes great care which takes time and leads to slow development. I think of C++ as worth it when this level of care is necessary to create a well-performing system. I would agree that most toy examples don't do a good job of explaining how to use RAII in a careful high performing way