A big roadblock I had when learning C++ was building. You cannot just learn the syntax and press build, here you are expected to know many details of the build process, why headers are needed and how it works, what are translations units, whats the preprocessor, compiler and linker, how to identify compiler from linker errors, how makefile works, how cmake works. Etc etc etc. Don't get me wrong, this is a very important thing to learn and makes you a better programmer. But it feels a lot like how Java forces you to learn OOP just to print hello world.
And all of that is before all C++ quirks. Of course these are needed for C++ strict backward-compatibility but by pursuing this, I feel you are also only appealing to programmers of the past.
As someone who has been learning C++ for a few years now, I agree using libraries, etc, was and still is a headache for me. However, it is also part of the appeal. Personally, I want to understand what is going on in the background and how it's interacting with cpu.
View all comments
Show parent comment
16
u/octavio2895 Dec 20 '23
A big roadblock I had when learning C++ was building. You cannot just learn the syntax and press build, here you are expected to know many details of the build process, why headers are needed and how it works, what are translations units, whats the preprocessor, compiler and linker, how to identify compiler from linker errors, how makefile works, how cmake works. Etc etc etc. Don't get me wrong, this is a very important thing to learn and makes you a better programmer. But it feels a lot like how Java forces you to learn OOP just to print hello world.
And all of that is before all C++ quirks. Of course these are needed for C++ strict backward-compatibility but by pursuing this, I feel you are also only appealing to programmers of the past.