No worries, that's the case for most people. You might want to keep an eye on it, though. It can be useful at times, especially when you need to repair your system.Balder wrote:I didn't live in the msdos ages and never used console for advanced things.
I don't think you need to delve into C++ too much, at least not for the ICN handling code. (I didn't take a closer look at the rest of the project, though.)Balder wrote:I'll look on that code then again and again. Furthermore, I'll read my c++ tutorials again, which I abandoned because c# was a better language for self teaching.
That's a very good approach. Having a specific goal is much more useful than simply reading about syntax and semantics. Just keep going, you'll eventually get there ...Balder wrote:I know that my knowledge on programming isn't enough to write a game nor a complex application, but I've been working on this as a kind of motivation to continue learning about programming.
If you feel that C# works for you, stay with it. Once you get the hang of the general concepts, switching between different languages becomes easier anyway.
I'm not a professional, but just a hobby programmer myself. But nevertheless I'd advise you to choose a language you're comfortable with. Don't buy statements telling you that language X is in every regard superior to language Y. All of them have their advantages and their disadvantages as well as their specific fields of application they're most useful in.Balder wrote:As you're a professional programmer, do you recommend me to use other languages than c# or c++?
My experience in graphical programming is limited, so I can't help you there. A general hint: Whether you choose to access DirectX or OpenGL directly or whether you choose to use a middle layer like SDL, always be sure to read the documentation and specifications.Balder wrote:or maybe other graphic framework than directx more suitable for begginners?
Anyway, good luck with your projects -- and you know where to come when you have file format issues.
