By using this site, you agree to our Privacy Policy and our Terms of Use. Close
TheRealMafoo said:

C is not inherently faster then C++. In some compilers, C++ is converted to C before it's compiled. Fortran is faster then C or C++. Because it does not use pointers it's easier for the compiler to optimize the code. It can do a better job of predicting when it needs to fetch something out of memory, and how long to keep values in registers.

It's why a lot of people who do a lot of CPU intensive calculations still use it. (Like blast analysis algorithms that might take 2 days to run)

As to the OP, it’s been said here before, but to reinforce the point… the language is not important. Learning what OOP is, and why you would use it, along with programming algorithms is what you want to focus on. Once you know those things, you’re in good shape. There are dozens of good languages, and based on what you plan on doing, you will be using different ones.

 


The first part of what you said about Fortran is complete BS.

Fortran is just more tailored for the task you described, that's all there is to it. Most CPU intensive clusters use C code actually, so please, stop spreading nonsense.

I'm surprised because the rest of what you said is actually correct, so how could you contradict yourself in the first part?

Anyway, what's important in programming, is understanding the concepts.  Being a good coder is different from being a good engineer. Asking how difficult is C++ is basically showing a great misunderstanding of what CS is. It's also showing total lack of knowledge about it.

If you didn't start programming at a very young age, it's already too late to be self-taught. CS courses are then mandatory IMHO, to understand even the basis of 3D programming. Programming involves knowing lots of things at more or less high levels, like maths, logic (math's derivative), signal processing, languages (of course), state machines (and all derivatives like automata and neural networks), algorithms, 3D programming and maths, databases, ...

Then, you'll be able to shake your heads and laugh at a lot of people here saying all kind of nonsense about game complexity compared to console power, or about how "hard is a console to program".

You'll actually be able to pick up easily who understand computer science and who doesn't (most people here don't). And no, it has nothing to do with number of polygons/s or fillrate...