   C/C++ and C#
  Before Posts/comments to this topic: I only want people that have used C# (and some Java) AND have used C++ before to reply to this post.My question is what do you think will be big in the future. C# or C++ still? I also wanted to know how different C# is from Java and C++. One of my Teachers at school said he favors C# than C++ and i want to know the benefits of using C# than C++. 
  Search the forums for the other dozen topics that ask exactly this in this and the general programming and lounge forums.Anyway, C# is catching on in quite a few places. Irregardless, if you like it use it. If you need it for a job use it. Otherwise don't, it's just a tool like any other language.   [edited by - woodsman on February 12, 2004 8:46:39 PM];  forget the future. This is what most people worry about. I know you don''t want to waste your time learning something that will become obsolete. But no one can predict that. Try both and use what you like most.    - Google - MSDN Library - GameDev.net Articles & Resources -  ;  leaning C++ teaches you most of what you need to know for C# ;quote:Original post by Gamedesign101  leaning C++ teaches you most of what you need to know for C#   and vice versa.    - Google - MSDN Library - GameDev.net Articles & Resources -  ;  I''ve used both and prefer C++ mainly because I hate how bloated visual studio 2003 has become compared to vc6. And if you ever write c# programs you immediately notice how much slower they are to straight c++. Not to mention you need to distribute .net dll with all your programs for them to run. Ok I admit this is becoming more of a visual c++ 6 vs visual studio 2003 but you''ll understand what I''m saying if you''ve use both.As far as you original question goes the way I see it and a lot of other professional programmers see the c++ vs c# question is this way:If your making windows apps stick with c# since that''s what microsoft is betting the future on and is tightly integrated into the OSIf you program any other OS or anything else for that matter stick with C++;  Studio .net is not the only C# compiler.. You can use Borland C# Builder.I prefer C++ over C#, mainly because I like to do my own memory allocation/deallocation (I know, I know.. i enjoy pain  ) But C#, imho is more powerfull than Java.The only thing that really matters though.. is what gets you a job. So learn all of them (they are not much different syntactically anyways) ;quote:Original post by daveangel  And if you ever write c# programs you immediately notice how much slower they are to straight c++. You do? ;  I''d stick with C++ and let C# mature a bit more before I learned it.  C# is a decent language, I just don''t see the advantage of using it.  I don''t make many allocation/deallocation mistakes any more.  C# is a stripped down version of C++, and right now I don''t see that C# is giving me anything for my sacrifice. ;quote:Original post by Martee  quote:Original post by daveangel   And if you ever write c# programs you immediately notice how much slower they peform compared to a c++ program. You do?   following is a good example especially since it involves game programming.How is the performance of the managed version?Initially, the managed version was faster than the native version when the default processor optimization setting /G5 (Pentium) was used. Changing the optimization setting to /G7 (Pentium 4 and Above) created a native version that runs around 15% faster then the managed version. Note, the assembly code was disabled for the native and managed versions so both versions are slower than the original Quake version.http://www.vertigosoftware.com/Quake2FAQ.htm  If God played dice, He''d win.—Ian Stewart, Does God Play Dice? The Mathematics of Chaos 