4 ms·
Speaking for myself: 1. I use a small amount of the surface area of C++, so the parts I don't use don't bother me 2. I may have silent footguns all over my co
by sevagh 2y ago
Speaking for myself:
1. I use a small amount of the surface area of C++, so the parts I don't use don't bother me
2. I may have silent footguns all over my code, but if I run my CMake build, and the tests pass, and the application does what I need from it, I really don't care
3. The up-front cost of writing correct/no-footgun code using Rust (as just one example) for me is much worse than the fluid "anything goes" of C++
>What copes do people employ to get over it to enable themselves to write C++?
C++ is powerful, flexible, and ubiquitous. Many third-party libaries in my daily toolbox are in C++, and I can re-use my code on Android, WebAssembly, cli applications, and any kind of project I may need to deploy. C++ skills are more widely available, such that maintaining C++ code is easier for companies (hiring employees, contractors, etc.) Delivering C++ code has me access to more clients and projects.
I can finish a C++ audio project for a client faster than I can figure out a `Ref<Arc<&'a static mut`, and they're happier for it.