3 ms·

I figured I'd get one of these types of comments. =) Yes, I know it is dangerous to lump C and C++ together. But truly, I appreciate your comment. Unix systems

by abnry 6y ago

I figured I'd get one of these types of comments. =) Yes, I know it is dangerous to lump C and C++ together. But truly, I appreciate your comment. Unix systems are important to me, and it seems C is probably a good idea to master first.

mondoshawan 6y ago
It's not dangerous -- it's a mistake. It's like putting strawberries in with salmon on a salad: ostensibly it's good, but it's wrong. :D C and C++ are really different languages these days. They share some syntax, but the ABIs and underpinnings of each are radically different. Their relationship these days is that of an estranged cousin: you are familiar with how it looks, but it is really not at all what it looks like anymore. Once the two languages shared dressing styles, but now, C++ has all these rebel < and > in places it should'nt. :)
ncmncm 6y ago
Learning C first would be a huge mistake. You will pick up bad habits that many people have never managed to shake, and that make for bad C++ and even bad Rust.
blub 6y ago
Learning C first would help you understand low level code, that much is true. But it's also probably the absolutely least productive programming language currently in use. Anything which doesn't involve twiddling bits or calling a function is tedious to write and hard to use. If you come from Python you'll have a shock when you see how little one line of C will get you. C++ and Rust don't suffer from this problem. You can go really low level, but you can also build abstractions and perhaps more importantly use existing ones.
sevensor 6y ago
You got about a dozen :) Don't be swayed by the naysayers who tell you not to learn C no matter what. You already know it's a dangerous language. Approach it from the perspective that this is your opportunity to learn what kind of headaches you want to avoid. Understand that the defensiveness and paranoia that come with writing C are not fundamental to systems programming, but that the problems that engender them are at the root of a lot of the complexity you'll see in other languages.
deleted 6y ago
[deleted]

by abnry 6y ago

mondoshawan 6y ago

It's not dangerous -- it's a mistake. It's like putting strawberries in with salmon on a salad: ostensibly it's good, but it's wrong. :D C and C++ are really different languages these days. They share some syntax, but the ABIs and underpinnings of each are radically different. Their relationship these days is that of an estranged cousin: you are familiar with how it looks, but it is really not at all what it looks like anymore. Once the two languages shared dressing styles, but now, C++ has all these rebel < and > in places it should'nt. :)

ncmncm 6y ago

Learning C first would be a huge mistake. You will pick up bad habits that many people have never managed to shake, and that make for bad C++ and even bad Rust.

blub 6y ago

Learning C first would help you understand low level code, that much is true. But it's also probably the absolutely least productive programming language currently in use. Anything which doesn't involve twiddling bits or calling a function is tedious to write and hard to use. If you come from Python you'll have a shock when you see how little one line of C will get you. C++ and Rust don't suffer from this problem. You can go really low level, but you can also build abstractions and perhaps more importantly use existing ones.

sevensor 6y ago

You got about a dozen :) Don't be swayed by the naysayers who tell you not to learn C no matter what. You already know it's a dangerous language. Approach it from the perspective that this is your opportunity to learn what kind of headaches you want to avoid. Understand that the defensiveness and paranoia that come with writing C are not fundamental to systems programming, but that the problems that engender them are at the root of a lot of the complexity you'll see in other languages.

deleted 6y ago

[deleted]