Comments by "Anony Mousse" (@anon_y_mousse) on "Python laid waste to my C++!" video.

Basically, the lesson of the day is this: if you don't know what you're doing or how the code translates into machine language, then you might as well just use Python. Granted, C++ does make it harder to understand even if you can see every construct that goes into your program, as "operator," demonstrates, but if you really want easy to understand and fast, then just use C.
37
@notthedroidsyourelookingfo4026 C does nothing for you. If the overall project isn't understandable, then that's on who programmed it. You can make your code clean and easy to understand.
4
@notthedroidsyourelookingfo4026 Hmm, yet another shadowed post, I guess I'll say it again. In C, you either write the tools yourself or you use one of the 4 billion third-party libraries. Namespaces are essentially permanent and `library_(function|type)` format, though I won't ever concede that C++ in any way does it better until I stop seeing std:: everywhere. I regularly pass arrays as a single parameter. Concise syntax can be had with macro magic, if you care to do so.
2
@breadiusloafus5068 Well, arrays in C are still indexed the same way, and smart pointers are just abstractions that you only need if you frequently make mistakes, and references are just fancy pointers that you can't change. As for implementing anything yourself, perhaps you've heard of a little thing call code reuse. I will admit that overloading operators makes things more concise, and that can make things quicker and easier to understand, but only if you don't write spaghetti code, and even then only if the operators chosen really make sense. In fact, operator overloading is the biggest reason why I still use C++ on a regular basis, but seriously, please don't ever use "operator," because it's the one operator that should never have been made overloadable.
2
@notthedroidsyourelookingfo4026 That's simply not true. I regularly pass arrays with only one parameter. Namespaces are a matter of manually including it for every function call and typename, and when I see more than a few percentage points of C++ programmers put a `using namespace XYZ;` in their code I'll concede the namespace point. You might have a point with operator overloading, but macro magic can negate the majority of that. Again, it all depends on the programmer because the language does scant little for you.
1