Will C# eventually pass C++? I just wanna’ know because I have a knack for learning something and the next day it becomes outdated.
Can you code WPF apps with C++?
Which one do you prefer?
Wow Jack you sure showed me.
Dick wad.
C++ has the advantage that you can find a compiler for almost any CPU made. It is also a lower level language than C# (meaning that TECHNICALLY you could write faster code though you will find in practice that slow code is almost always a design issue). C++ has also been around a very long time.
However… there are a lot more jobs for C# (and java) at the moment. C#’s learning curve is far less than that of C++ and it integrates very well with WPF. If you are looking to produce code quickly, C# is where its at. C# is a "safer" language, and with internet trust issues, security, multi-threading, pointer safety, you get a leg up in C# with automatic support. C# supports reflection, lambda functions, and a slew of other things missing from C++ (include file hell, for instance).
This whole "which is better A or B" can quickly digress into a religious war. It is almost always accompanied by some elitist ivory tower snob who will call you a "noob" for asking the question (without offering insight). It is better to ask for the advantages of one over the other. I have fond memories of C++, Smalltalk, C, Lisp, Assembly language(s), but I realize that to take advantage of a lot of new technologies out there, it’s important to adapt, so I write primarily in Java and in C# at the moment (well, and python, XSLT, PHP, et al.).
So… Of the two languages you asked about, I would recommend C#, and definitely learn WPF (including Silverlight) — even if it doesn’t survive, it is a <INSERT OPINION HERE> architectural approach to separation of concerns in GUI design. With C# you won’t feel so behind the curve. When you use some nifty new feature, just remember to ask yourself WHY it is so nifty and what pain was it intended to resolve.
September 27th, 2009 at 6:35 pm
I doubt C# will pass C++. C++ still generates faster code than C#. C# also requires that .NET framework be installed on the computer. After all, C# was based on Java.
References :
September 27th, 2009 at 7:22 pm
I prefer C++. And, although C# is getting popular faster than the speed of light (Sorry, Einstein!), I think C++ could still live as it’s.. different, not to forget the Unix system.
Anyway, they are very similar, and I say that knowing about it. So, when you choose to learn one of them, if you do decide later to learn the other, it would only need a little work.
Don’t think you can write WPF in C++ per se, but C++ is one of the most powerful languages, and so you can do whatever WPF fdoes by working harder.
References :
September 27th, 2009 at 8:11 pm
C++ has the advantage that you can find a compiler for almost any CPU made. It is also a lower level language than C# (meaning that TECHNICALLY you could write faster code though you will find in practice that slow code is almost always a design issue). C++ has also been around a very long time.
However… there are a lot more jobs for C# (and java) at the moment. C#’s learning curve is far less than that of C++ and it integrates very well with WPF. If you are looking to produce code quickly, C# is where its at. C# is a "safer" language, and with internet trust issues, security, multi-threading, pointer safety, you get a leg up in C# with automatic support. C# supports reflection, lambda functions, and a slew of other things missing from C++ (include file hell, for instance).
This whole "which is better A or B" can quickly digress into a religious war. It is almost always accompanied by some elitist ivory tower snob who will call you a "noob" for asking the question (without offering insight). It is better to ask for the advantages of one over the other. I have fond memories of C++, Smalltalk, C, Lisp, Assembly language(s), but I realize that to take advantage of a lot of new technologies out there, it’s important to adapt, so I write primarily in Java and in C# at the moment (well, and python, XSLT, PHP, et al.).
So… Of the two languages you asked about, I would recommend C#, and definitely learn WPF (including Silverlight) — even if it doesn’t survive, it is a <INSERT OPINION HERE> architectural approach to separation of concerns in GUI design. With C# you won’t feel so behind the curve. When you use some nifty new feature, just remember to ask yourself WHY it is so nifty and what pain was it intended to resolve.
References :