[quote name='UltimaX' timestamp='1315924056' post='4861089']
Game Maker, RPG Make, XYZ Maker, etc are good, but it's also a double edged sword. You are learning a proprietary language / script that is of no use once you are done with it. What if he decides next year he is done with games and wants to move to application development? He would have to start all over now to learn another language. That's why I think it's best to learn a standard language. Teaches you the same logic and what not, but you are also learning a lot more about the system you are on (file system, Win32 API (for example), etc.

When you get into college, the first thing you learn is a pseudo language. It will not be of any use in the future, but will help you the general structure of an algorithm. Thats the reason I pointed in the RPG Maker direction. Sure you wont be able to use it in the future, but a lot of learning how to program is learning how to program, language independent, isnt it so?
[/quote]

Yes that is true, but that's also college. I was thinking more along the lines of something that can be applied and have some value in the future. C# was just a suggestion because once you start learning DirectX or OpenGL you can still use C# for the tools creation. You have to learn from scratch either way you go as well. So there is still the value there in C# and more beneficial. Not saying RPG Maker is a wrong choice, but I just wanted to make James aware of the pros and cons.

Lego Mindstorm

Granted, it will bankrupt you, but it is the absolute perfect introduction to programming for a 10 year old. Additionally as it gets more complex you can actually "extend" the programming language with much more complex programming.

Oh, and italics, ew. Your post was literally extremely difficult to read. Also, I almost completely dismissed it as spam because of the font/italics/pink.

I never would have thought of it myself, but Lego Mindstorm is an inspired suggestion. My housemate mentored a team of kids with some kind of Mindstorm challenge that IBM held on their local campus a couple months ago, and had nothing but good things to say about the kits and the experience and fun the kids had. And he's a techie, but no programmer—he works in IBM's HR department. So I'd think you have a fair shot of being able to help your son out when he gets stuck.

If you do decide to start with something more standard, C# probably isn't a bad way to go. But I'd recommend you learning it alongside or slightly ahead of him. And you both can ask questions here.

And, please, nix the italics and pink text

[quote name='arthurviolence' timestamp='1315925142' post='4861100']
[quote name='UltimaX' timestamp='1315924056' post='4861089']
Game Maker, RPG Make, XYZ Maker, etc are good, but it's also a double edged sword. You are learning a proprietary language / script that is of no use once you are done with it. What if he decides next year he is done with games and wants to move to application development? He would have to start all over now to learn another language. That's why I think it's best to learn a standard language. Teaches you the same logic and what not, but you are also learning a lot more about the system you are on (file system, Win32 API (for example), etc.

When you get into college, the first thing you learn is a pseudo language. It will not be of any use in the future, but will help you the general structure of an algorithm. Thats the reason I pointed in the RPG Maker direction. Sure you wont be able to use it in the future, but a lot of learning how to program is learning how to program, language independent, isnt it so?
[/quote]

Yes that is true, but that's also college. I was thinking more along the lines of something that can be applied and have some value in the future. C# was just a suggestion because once you start learning DirectX or OpenGL you can still use C# for the tools creation. You have to learn from scratch either way you go as well. So there is still the value there in C# and more beneficial. Not saying RPG Maker is a wrong choice, but I just wanted to make James aware of the pros and cons.
[/quote]

Of course mate, I completely understand your point. Lets just not forget that he's still 10 years old, and will have to do a lot of starting over during his life in this world. (Which arent actually starting ALL over again, just relearning a few things in a different way), but I do understand your point of starting already facing some real world things being beneficial, and it makes total sense.

When I was a kid, I enrolled in a number of summer computer camps between the ages of maybe 8 and 14. They taught me Visual Basic, HTML, C, C++ and Java. Of them, the only one that lent me any lasting knowledge was the course in HTML, and maybe the tiniest bit of C.

In university, I took an introduction to programming in C. For once, they actually taught me how things worked rather than just what to do. Suddenly, everything made sense. From that point onward, learning a new programming language was really just a matter of time.

The point of this story is... Well, I don't really have one, except perhaps that you should probably not worry too much about doing 'real' programming. If your son enrols in engineering or computer science, they'll get him a real teacher to explain things. They'll give him the tools to do things at a professional level. Until then, working with simplifying tools like Lego Mindstorms or GameMaker is not a bad idea.

Game Maker, RPG Make, XYZ Maker, etc are good, but it's also a double edged sword. You are learning a proprietary language / script that is of no use once you are done with it. What if he decides next year he is done with games and wants to move to application development? He would have to start all over now to learn another language. That's why I think it's best to learn a standard language. Teaches you the same logic and what not, but you are also learning a lot more about the system you are on (file system, Win32 API (for example), etc.

I wouldn't wish the Win32 API on my enemies, let alone some poor kid trying to learn to program. It's confusing, full of bad practices and stuffed with legacy cruft. Just setting up a window that you can close takes dozens of lines of boilerplate code. And it's unnecessary; you can spend years working professionally in application development on Windows without having to deal with it if you just use a 3rd-party toolkit.

Besides, it's good practice to learn a few new languages.