Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. C++ vs. C#

C++ vs. C#

Scheduled Pinned Locked Moved The Lounge
c++questioncsharpvisual-studiolearning
5 Posts 5 Posters 1 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    Miguel Soto
    wrote on last edited by
    #1

    A new programming language is coming for next generation of programmers: C#. Currently I am learning C++ and I love programming in Visual C++ but because of that new language I am not sure if giving up this learning and go straight to C#. Is someone thinking the same I am about this situation? What is recommended? :confused: Miguel

    C A 2 Replies Last reply
    0
    • M Miguel Soto

      A new programming language is coming for next generation of programmers: C#. Currently I am learning C++ and I love programming in Visual C++ but because of that new language I am not sure if giving up this learning and go straight to C#. Is someone thinking the same I am about this situation? What is recommended? :confused: Miguel

      C Offline
      C Offline
      Christian Graus
      wrote on last edited by
      #2

      Is the first line of your post a direct quote from M$ hype ? C# is, according to M$, necessary because VB is limited and C++ is too hard. C# will only compile to the CLR, C++ will still compile to native code. By all means have a look at C#, I intend to when my beta CD arrives, but it would be extremely foolish to ditch C++ at this stage, or ( IMHO ) anytime in at least the next 10 years. Christian #include "std_disclaimer.h" People who love sausage and respect the law should never watch either one being made. The things that come to those who wait are usually the things left by those who got there first.

      C W 2 Replies Last reply
      0
      • M Miguel Soto

        A new programming language is coming for next generation of programmers: C#. Currently I am learning C++ and I love programming in Visual C++ but because of that new language I am not sure if giving up this learning and go straight to C#. Is someone thinking the same I am about this situation? What is recommended? :confused: Miguel

        A Offline
        A Offline
        Anders Molin
        wrote on last edited by
        #3

        I think it depends on the applications you make. It is going to take some time before everyone have the CLR on their desktop's, and until they do, they can't run C# programs. I spend almost my time writing server applications, and I _do_not_ want to write those in a language that can't compile native exe's. I want speed and low memory usage, and I don't think C# can give me that. (and I love pointers ;) ) I have been playing around with C# Beta2, and I think that for web it's a _great_ language. :) And when ppl. get the CLR on their desktops, I also think it's going to be great to make GUI stuff. (If speed is not that big an issue) Just my 2 cents - Anders Money talks, but all mine ever says is "Goodbye!"

        1 Reply Last reply
        0
        • C Christian Graus

          Is the first line of your post a direct quote from M$ hype ? C# is, according to M$, necessary because VB is limited and C++ is too hard. C# will only compile to the CLR, C++ will still compile to native code. By all means have a look at C#, I intend to when my beta CD arrives, but it would be extremely foolish to ditch C++ at this stage, or ( IMHO ) anytime in at least the next 10 years. Christian #include "std_disclaimer.h" People who love sausage and respect the law should never watch either one being made. The things that come to those who wait are usually the things left by those who got there first.

          C Offline
          C Offline
          CodeGuy
          wrote on last edited by
          #4

          Christian, you've got both guns blazing today. :/ I think more accurately, MS's view is that C++ and COM (together) is much harder than it should be. Which, having done both, is a true statement. C# is the future of COM/Windows programming, but it will take a while to get here. I don't think any time spent learning the elements behind .NET (COM, Win32 API) is time wasted. For yet another viewpoint, see http://www.sellsbrothers.com/spout A consideration as well for C# is whether you even have the metal to run it. The VS.NET IDE chokes on 128MB of RAM; I wouldn't bother running it with less than 256MB. (I guess MS says 192MB is acceptable for beta 2, but why don't I believe them?) Of course you can always use the command line tools. (Bleah.)

          1 Reply Last reply
          0
          • C Christian Graus

            Is the first line of your post a direct quote from M$ hype ? C# is, according to M$, necessary because VB is limited and C++ is too hard. C# will only compile to the CLR, C++ will still compile to native code. By all means have a look at C#, I intend to when my beta CD arrives, but it would be extremely foolish to ditch C++ at this stage, or ( IMHO ) anytime in at least the next 10 years. Christian #include "std_disclaimer.h" People who love sausage and respect the law should never watch either one being made. The things that come to those who wait are usually the things left by those who got there first.

            W Offline
            W Offline
            William E Kempf
            wrote on last edited by
            #5

            Even though I agree that ditching C++ for C# is foolish, you've got some facts wrong. C# compiles to the CLR, yes, but this in turn can be compiled to native code and it can all occur with the press of a single button in VisualStudio.NET. So there's little point in mentioning this. Not to mention it's quite possible that there could be a C# compiler that never produces CLR byte codes. William E. Kempf

            1 Reply Last reply
            0
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • World
            • Users
            • Groups