Use whatever language you enjoy the most. The concepts needed to make a game aren't specific to a language. To figure out what language you like the most, you need to actually try them for yourself. I use C# because I enjoy it the most. Alternatively, stick with what you know unless you feel bored and want to try something new. AS3 is relatively well suited to learning how to program, especially if you want to integrate some 2D graphics easily.
Worry about performance LAST. Your primary job is making your program do things *correctly*. After things are working correctly, if you feel like performance sucks, use a profiling tool on the program to find where the slow parts are, and rewrite each small portion of your program to make it fast enough. Only if you are unable to do this should you consider switching languages for performance's sake.
If you do it right, the majority of your time will be spent adding small features, testing them, and rewriting things when you feel like it would improve your program. You shouldn't have to fight with your programming language.
(Edit)
I want to slightly amend my second paragraph: Worry about performance *when it actually impacts what you're doing*. For example, if you can't quickly test what you're working on because something is taking too long, it might make you drastically more productive if you remove that bottleneck right away.
Show differencesHistory of post edits
#3Nypyren
Posted 08 March 2012 - 12:40 AM
Use whatever language you enjoy the most. The concepts needed to make a game aren't specific to a language. To figure out what language you like the most, you need to actually try them for yourself. I use C# because I enjoy it the most. Alternatively, stick with what you know unless you feel bored and want to try something new. AS3 is relatively well suited to learning how to program, especially if you want to integrate some 2D graphics easily.
Worry about performance LAST. Your primary job is making your program do things *correctly*. After things are working correctly, if you feel like performance sucks, use a profiling tool on the program to find where the slow parts are, and rewrite each small portion of your program to make it fast enough. Only if you are unable to do this should you consider switching languages for performance's sake.
If you do it right, the majority of your time will be spent adding small features, testing them, and rewriting things when you feel like it would improve your program. You shouldn't have to fight with your programming language.
(Edit)
I want to slightly amend my second paragraph: Worry about performance *when it actually impacts what you're doing*. For example, if you can't quickly test what you're working on because something is taking too long, it might make you drastically more productive if you remove that bottleneck.
Worry about performance LAST. Your primary job is making your program do things *correctly*. After things are working correctly, if you feel like performance sucks, use a profiling tool on the program to find where the slow parts are, and rewrite each small portion of your program to make it fast enough. Only if you are unable to do this should you consider switching languages for performance's sake.
If you do it right, the majority of your time will be spent adding small features, testing them, and rewriting things when you feel like it would improve your program. You shouldn't have to fight with your programming language.
(Edit)
I want to slightly amend my second paragraph: Worry about performance *when it actually impacts what you're doing*. For example, if you can't quickly test what you're working on because something is taking too long, it might make you drastically more productive if you remove that bottleneck.
#2Nypyren
Posted 07 March 2012 - 11:53 PM
Use whatever language you enjoy the most. The concepts needed to make a game aren't specific to a language. To figure out what language you like the most, you need to actually try them for yourself. I use C# because I enjoy it the most. Alternatively, stick with what you know unless you feel bored and want to try something new. AS3 is relatively well suited to learning how to program, especially if you want to integrate some 2D graphics easily.
Worry about performance LAST. Your primary job is making your program do things *correctly*. After things are working correctly, if you feel like performance sucks, use a profiling tool on the program to find where the slow parts are, and rewrite each small portion of your program to make it fast enough. Only if you are unable to do this should you consider switching languages for performance's sake.
If you do it right, the majority of your time will be spent adding small features, testing them, and rewriting things when you feel like it would improve your program. You shouldn't have to fight with your programming language.
Worry about performance LAST. Your primary job is making your program do things *correctly*. After things are working correctly, if you feel like performance sucks, use a profiling tool on the program to find where the slow parts are, and rewrite each small portion of your program to make it fast enough. Only if you are unable to do this should you consider switching languages for performance's sake.
If you do it right, the majority of your time will be spent adding small features, testing them, and rewriting things when you feel like it would improve your program. You shouldn't have to fight with your programming language.
#1Nypyren
Posted 07 March 2012 - 11:52 PM
Use whatever language you enjoy the most. The concepts needed to make a game aren't specific to a language. To figure out what language you like the most, you need to actually try them for yourself. I use C# because I enjoy it the most. Alternatively, stick with what you know unless you feel bored and want to try something new. AS3 is relatively well suited to learning how to program, especially if you want to integrate some 2D graphics easily.
Worry about performance LAST. Your primary job is making your program do things *correctly*. After things are working correctly, if you feel like performance sucks, use a profiling tool on the program to find where the slow parts are, and rewrite each small portion of your program to make it fast enough.
If you do it right, the majority of your time will be spent adding small features, testing them, and rewriting things when you feel like it would improve your program. You shouldn't have to fight with your programming language.
Worry about performance LAST. Your primary job is making your program do things *correctly*. After things are working correctly, if you feel like performance sucks, use a profiling tool on the program to find where the slow parts are, and rewrite each small portion of your program to make it fast enough.
If you do it right, the majority of your time will be spent adding small features, testing them, and rewriting things when you feel like it would improve your program. You shouldn't have to fight with your programming language.