There is no consensus about it, but I fully agree that C++ is majorly used for game creation, because of it's speed, free tools and libraries. Also, I agree, after learning C++ you can learn and understand C#, Java, JS and Python code very easily.

There is no language directed right at games creation, but if you want to create game as quickly as possible - you should look at JavaScript. It won't allow you to create very computational-heavy game, but it will give you rapid start.

i don't care what you guys choose but i support c++, with it you could even program games for consoles and learning it makes it easy to learn others. why not spend a little more time and more hard-work to learn c++ and achieve...???

on of the book i am using to learn which is great and really understandable. It is also a friendly version, click here to see it in google books, amazon selling the book, or if you are not able to buy the book like me, send me a pm and i will send you a pdf file of the book xD

You can't go wrong with either C++ or Java as a primary language. C++ is the darling of the games industry whilst Java can be used for Android games.

However, if you are learning from scratch then its wise to leave alone OOP languages until you have the basics of structured programming nailed. Both C or JavaScript are ideal beginner languages and share almost identical basic syntax with both C++ and Java. Well, C and C++ are considered the same language but there are some differences beside the obvious use of OOP in C++...

This is bad advice, IMO. Firstly, because OOP is a good thing to learn early, so you should start with an OOP language. Secondly, because when learning C as a precursor to C++ there are a number of things that are common practice in c, that are bad practice in C++.

C and C++ are different languages, and not just because of OOP. Two big differences are how to write constants, and how to write generic code.

I've decided to go with C# as many people have pointed out here that for a beginner it's easier than c++. Someone also mentioned that C# goes hand in hand with unity and I am looking at learning that also. As my long term goal is to program for games this seems to be the logical choice.

Thanks once for for your invaluable suggestions and information.

Cheers,

Rhino.

I've decided to go with C# as many people have pointed out here that for a beginner it's easier than c++. Someone also mentioned that C# goes hand in hand with unity and I am looking at learning that also. As my long term goal is to program for games this seems to be the logical choice.

Thanks once for for your invaluable suggestions and information.

Cheers,

Rhino.

ya, good but without learning c++ you need to go with using engines to power up your games and your game will be based on the engine, not in you own skill of programming :(

I've decided to go with C# as many people have pointed out here that for a beginner it's easier than c++. Someone also mentioned that C# goes hand in hand with unity and I am looking at learning that also. As my long term goal is to program for games this seems to be the logical choice.

Thanks once for for your invaluable suggestions and information.

Cheers,

Rhino.

ya, good but without learning c++ you need to go with using engines to power up your games and your game will be based on the engine, not in you own skill of programming

Baby steps. Gotta walk before I can run :)

I've decided to go with C# as many people have pointed out here that for a beginner it's easier than c++. Someone also mentioned that C# goes hand in hand with unity and I am looking at learning that also. As my long term goal is to program for games this seems to be the logical choice.

Thanks once for for your invaluable suggestions and information.

Cheers,

Rhino.

ya, good but without learning c++ you need to go with using engines to power up your games and your game will be based on the engine, not in you own skill of programming

Baby steps. Gotta walk before I can run

True :)

Sigh...please read my post properly before replying...



"Well, C and C++ are considered the same language but there are some differences beside the obvious use of OOP in C++..."

That statement is still incorrect, no matter how you emphasize it. They are nowhere near considered the same language, and there are many differences. Their standards move at different paces, and disregarding even OOP, there are a surprisingly large amount of things that C supports and allows that C++ does not, and vice versa. Not to mention, a wealth of different keywords (and meanings for them), with new types that are exclusive to C or C++. C++ started out before the first ANSI C standard; it is in many ways not a superset of the language, because it wasn't wholly built upon it. In many ways, it was influenced by the success of C as a programming language, and borrowed its syntax, but it was developed alongside it, and separately.

To keep saying that they are almost the same is just not true. There are many code samples that will compile differently (or not at all) in either language. Perhaps try to elaborate on your point so that you don't confuse newcomers? That's the reason people are calling you on it.

Anyway, I think learning OOP straight off the bat is going to leave many beginners feeling lost. I've seen it on the courses I have taken where some have withdrawn because they jumped the gun with procedural programming. One has enough on their plate with loops, control statements, data types, opening and closing files without throwing OOP in to the mix. Yes, its an important concept, but one thing at a time, no?

I agree with this, but it might depend on the teacher. My teacher for C++ was terrible. She didn't know what she was doing, and was teaching C with Classes. Everything went in a class, even things that held no state; they should have been free functions in a namespace, but she didn't teach namespaces. We had char arrays for everything, because she didn't teach the standard templates. We got ripped off in our education. As a result, my code was absolutely horrible, and it took me many years of finally swearing off classes because I didn't need them, before I could learn how important they were.

Often, going without a feature and doing things the hard way is the best way to learn to appreciate a feature.