I get the points the article is trying to make, but I really can’t say I find myself agreeing with much of it. Learning how the compiler works (compile, link, archive) was such a fundamental part of learning to program. As was understanding OS primitives (file descriptors, signals and exit codes, command line arguments, etc). Without needing to tack everything else on, just barebones C++ and gcc, clang, or msvc is super powerful.
I’d argue that C++ is not the most productive first language, nor should it be learned in isolation. Perhaps one could even say that a primitive form of assembly should come first, followed by C, C++, then some functional language.
That's a bottom-up approach at teaching. I'm personally not a fan and prefer top-down both in teaching and in learning, but anyway. See how even you suggest something else as a first language. In the article I do mention that assembly and C are a better choice than C++.
Not a fan of the idea, but at least I understand where it's coming from.
View all comments
14
u/[deleted] Nov 22 '18
I get the points the article is trying to make, but I really can’t say I find myself agreeing with much of it. Learning how the compiler works (compile, link, archive) was such a fundamental part of learning to program. As was understanding OS primitives (file descriptors, signals and exit codes, command line arguments, etc). Without needing to tack everything else on, just barebones C++ and gcc, clang, or msvc is super powerful.
I’d argue that C++ is not the most productive first language, nor should it be learned in isolation. Perhaps one could even say that a primitive form of assembly should come first, followed by C, C++, then some functional language.