> With C code, there’s no going into a program without fully knowing what it’s going to do at every step of the way... This guy seems to be putting C on a pede

> With C code, there’s no going into a program without fully knowing what it’s going to do at every step of the way... This guy seems to be putting C on a pedestal. It's OK, for certain jobs. Like kernels, CLI utilities, C/C++ for games, etc. But even there Rust and Go and other tools are invading that space and doing well. When I want to make something, I usually use whatever I think can get me to something usable fast. C is rarely the answer. I think the same holds for someone trying to learn programming. Python or Go removes a lot of cruft that new programmers shouldn't have to deal with, at first. They are good intros to "you want X? Well import X, then start using X.foo" instead of "You want X, well first let's start a Makefile so we can get our libs linked in properly depending on if this is debug or release, and then maybe CMake so we can use it on other systems, and so on and so forth..."