Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Armok]

I myself am a Python man, but I've started to pick up a bit of C#.

At the end of the day, the language you want to use is the one that makes you feel the most comfortable using and satisfies the list of requirements needed for the project at hand. If you love C, find a way to make it work for you. If you love Java, ignore the haters, and just use it. Find something that you not only can program in, but want to program in. These days, nearly every language available has all the libraries ported that you'd ever want to use, anyway. So just go out there and start with a few Hello Worlds. Whatever one makes you want to write more in, that's the language you choose.

Compiled, interpreted, JIT, high-level, low-level, whatever. The secret is, at the end of the day, it doesn't matter one fucking bit what the hell you program in. The end-user doesn't give two shits about what work went into the program, only that it works full stop. So just code.

[Puzzlemaker]

Learn Brainfuck.

[Starver]

Learn Brainfuck.

(That falls foul of this system's web filters, for obvious reasons.

Or maybe Whitespace...

[Hippoman]

I want to learn C!
I really do, but everyone keeps telling me that C doesnt have objects in text and classes. And then because of that I cant use WinApi to make windows :C

[Dasleah]

I want to learn C!
I really do, but everyone keeps telling me that C doesnt have objects in text and classes. And then because of that I cant use WinApi to make windows :C

So what we have there is exactly what I was talking about - the language you use is the one that meets the requirements for whatever the project is at hand. C doesn't offer you the features needed for the project you want to produce, so it's time to move on.

If you're really wanting to still learn C, then pick up some C++. It was originally called C With Classes for a reason, you know. C++ will give you the classes you want, but everything else inbetween that can still be written in C, if I recall correctly.

And for coding in that, I recommend picking up Visual C++ 2008 Express Edition free from Microsoft. So bam, there's your language and your IDE ready to go.

[Alexhans]

Dasleah... you're my new favourite b12-er... 

[Hippoman]

Dasleah... you're my new favourite b12-er... 

[Zombie0hour]

Hippo its really all about personal preference. Muck around in every language you can and pick a few. There are thousands of languages out there, and I find many of the obscure ones are the most fun to use.

[qwertyuiopas]

I want to learn C!
I really do, but everyone keeps telling me that C doesnt have objects in text and classes. And then because of that I cant use WinApi to make windows :C

What? Can't make windows in C? That's an utter lie(or misconception), I have been directly using the windows API from C ever since I copied some tutorial's code(And have been slowly getting more interested in alternate parameters, but since all of the basics are already there, I don't have to bother with anything until I feel like it)

Also, you can fake a class in C with function pointers in a struct, and create them with a function that returns ({probably optional}a pointer to) one of them, though if you care so much about them, maybe C++ would be better.


Bottom line: If you are not learning from a real person, it will take longer, but you can still get the same results(an education).
And C and C++ can both do almost anything.

[Alexhans]

John Nash: "Classes will dull your mind"

Spoiler (click to show/hide)

Me: "Should I be using structs, instead?" 

Spoiler (click to show/hide)

Lame joke WARNING!!!

Spoiler (click to show/hide)

Too late!!!   

[deadlycairn]

Honestly, if you don't have a teacher, I wouldn't recommend starting with C++, Java, C, Python, Assembly or any other 'real' programming language.

Since you said one of the main reasons you are learning to program is to make games (let's be honest, that's EVERYBODIES main reason ), I'm going to recommend you actually start out with a game making tool. The aptly-named Gamemaker is a good start. People may hate me for recommending it - admittedly it's not a 'real' programming language. Hell, if you want you don't need to use any code at all. HOWEVER, it gives you a wonderful grasp in the basic parts of putting together a working application, and will slowly ease you into programming. It DOES come with a scripting language for you to use, which will again, help the transition when you decide to start learning a 'real' language. The best part of these tools, however, is the fact that STRAIGHT AWAY you can see the things you've put into the game given shape. Discouragement will be your biggest hurdle, and I always fall off the boat after a long period of coding with little visible gain in my application.

Basically, ease yourself in, with something simpler. Don't go with the hardest language for tough points. Go with something you find enjoyable, that will last you the long run. And, as the Spelunky and Battleships Forever will show, some really awesome games can be made with tools.

[IndonesiaWarMinister]

Oh...

I thought Construct > Gamemaker?

Yeah, I'm learning to make a game BEFORE I finished learning to program.
This will get VERY messy.

[Alexhans]

It DOES come with a scripting language for you to use, which will again, help the transition when you decide to start learning a 'real' language.

Yes... But you will have so many vices to remove that it will be hell when you try to move from one to another.

He must learn a basic programming tutorial instead of just jumping into game making.  Game making is not just about programming.  It involves game design, graphics management, etc, etc... wich add a lot of distractions in the programmers way...

I think it's much better to start with basic programming tutorials to learn the logic and the tools you're going to use.  Bear with it, do exercises and then start making things on your own (wich is where the experience will come).

Doing things the "quick way" hardly pays off.

[qwertyuiopas]

Linux didn't start from nothing, it started with a base and slowly phased it out as people wrote new code. That way, the results could be seen from the start.

At first, it would be better to start with code from a tutorial so that it works, and add your own code as you learn, replacing the tutorial's basics with custom code.

[eerr]

What should i learn.

What do you want to do?