"Poll" Has C# Generally Replaced C++

[Guest]

Is it your general opinion that C# is generally designed/intended/ready to
replace C++? I know the answer is not black and white but please repond YES
or NO (add any comments if you would like)

I just thought it might be interesting to get a tally. This is related to a
previous thread. So far we have two NOs from "aa" and Bo Persson.

 

[Guest]

By the way my vote is YES even though I know C++ can have advantages and is
still valuable/required for many purposes.

 

[William DePalo [MVP VC++ ]]

Is it your general opinion that C# is generally designed/intended/ready to
replace C++? I know the answer is not black and white but please repond
YES
or NO (add any comments if you would like)

No, it is not.

In a few years it may be the language most often used to _build_
applications for Windows, but the operating system and its drivers will
continue to be written in C or C++ for the near term at least.

Regards,
Will

 

[Carl Daniel [VC++ MVP]]

Is it your general opinion that C# is generally
designed/intended/ready to replace C++? I know the answer is not
black and white but please repond YES or NO (add any comments if you
would like)

I just thought it might be interesting to get a tally. This is
related to a previous thread. So far we have two NOs from "aa" and Bo
Persson.

No. C# is a language designed, intended and ready to replace Java (and well
on it's way to doing so).

C++ is still better at nearly all the things C++ has always been better at.

-cd

 

[Willy Denoyette [MVP]]

Is it your general opinion that C# is generally designed/intended/ready to
replace C++? I know the answer is not black and white but please repond
YES
or NO (add any comments if you would like)

I just thought it might be interesting to get a tally. This is related to
a
previous thread. So far we have two NOs from "aa" and Bo Persson.

From a pure language point of view....
Designed & Intended to: NO
Ready to: NO
Some might say it's "ready to", but I guess this is only a personal
interpretation and only reflects their own requirements. There are simply
too many problem domains that aren't covered yet (although, this is not
strictly a language issue) , and I don't even consider the lack of platforms
availbility.

Willy.

 

[Guest]

5 NOs and only one YES (mine).

I guess my next question is then why would Microsoft call it C# which is:
C++
++ ?

The implication is that C# is to C++ as C++ was to C.

 

[Jochen Kalmbach [MVP]]

Hi Greg!

Is it your general opinion that C# is generally designed/intended/ready to
replace C++? I know the answer is not black and white but please repond YES
or NO (add any comments if you would like)

I just thought it might be interesting to get a tally. This is related to a
previous thread. So far we have two NOs from "aa" and Bo Persson.

Your question is a bit confusing...
You need to ask the "right" question to get the "right" answer!

For example: Will C# replace C++ in some small areas like UI?


--
Greetings
Jochen

My blog about Win32 and .NET
http://blog.kalmbachnet.de/

 

[Nemanja Trifunovic]

No. C# is really VB with curly braces. C++ is a very different language.

 

[Guest]

For application programming C++ seems to be losing some ground according to
InfoWorld's Developer's survey:

java +34%
C# +23%
C/C++ -3%

 

[None]

5 NOs and only one YES (mine).

I guess my next question is then why would Microsoft call it C# which is:
C++
++ ?

Perhaps your next question should really be will C++/CLI replace C#? )))

 

[Bo Persson]

For application programming C++ seems to be losing some ground
according to
InfoWorld's Developer's survey:

java +34%
C# +23%
C/C++ -3%

And they can't differentiate between the languages either. Who knows,
perhaps this means C -10%, C++ +7%?


Bo Persson

 

[Carl Daniel [VC++ MVP]]

For application programming C++ seems to be losing some ground
according to InfoWorld's Developer's survey:

java +34%
C# +23%
C/C++ -3%

I would suspect a poll in InfoWorld to be very highly skewed towards IT-shop
development and not representative of commercial application development
which is still dominated very strongly by C++.

-cd

 

[Andre Kaufmann]

[...]
No, it is not.

In a few years it may be the language most often used to _build_
applications for Windows, but the operating system and its drivers will
continue to be written in C or C++ for the near term at least.

And yet Microsoft experiments with a research operating system written
in C#.

Regards,
Will

Regards,
Andre

 

[Bob Moore]

Is it your general opinion that C# is generally designed/intended/ready to
replace C++? I know the answer is not black and white but please repond YES
or NO (add any comments if you would like)

No.

It was designed to compete with Java, not C++. A different horse on a
very different course.

--
Bob Moore
http://bobmoore.mvps.org/
(this is a non-commercial site and does not accept advertising)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Do not reply via email unless specifically requested to do so.
Unsolicited email is NOT welcome and will go unanswered.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

[William DePalo [MVP VC++ ]]

And yet Microsoft experiments with a research operating system written in
C#.

Yup. I've seen at least a couple of videos on MSDN's Channel 9 on the
subject of ongoing research into operating systems and driver development
with managed code.

Still, my guess is that a manged o/s for some real-world purpose is a
half-decade away and for general purposes it is likely to be at least twice
as far off as that.

Of course, no one important shares his long range plans with me so I could
be all wrong. ;-)

Regards,
Will

 

[Arnaud Debaene]

I guess my next question is then why would Microsoft call it C# which
is: C++
++ ?

Are you *really* trying to understand marketing naming woodoo from a
pragmatic ant technical point of view ;-)

Arnaud
MVP - VC

 

[Nishant Sivakumar]

For .NET 2.0, C++/CLI lets you do everything C# can + a lot more - so it's
definitely your better option.

For Longhorn, I am not so sure. There's no direct XAML support for C++. So
you are going to have to hand-code your UIs (and unless all your apps have
simple dialogs with 1-3 controls on them, that's a pain in the neck). Of
course, maybe they are working on XAML support for C++ too, and if so,
there's no reason to use C#

 

[Guest]

I think C# is a general replacement for C++ even though C++ has its place.

C was a quick "throw-together" language at Bell Labs that took hold. C++ was
built on top of C an carried the syntax.

C# has superior syntax. In C/C++ both the pointer declaration and the object
of the pointer use a * . Also C# array are declared as a type rather than
type/context:

e.g. int[] x; v.s. int x[];

C# has the advantage of practical "non-rushed" thinking in its design.

Again. I don't deny that C++ has its place and can have advantages. However,
I think C# is the "general" replacement for C++. People may not fully realize
it yet. That is my opinion.

 

[Bo Persson]

I think C# is a general replacement for C++ even though C++ has its
place.

C was a quick "throw-together" language at Bell Labs that took hold.
C++ was
built on top of C an carried the syntax.

C# has superior syntax. In C/C++ both the pointer declaration and
the object
of the pointer use a * .

C++ also introduced the reference, to reduce the use of pointers.

I also object to the use of C/C++ to denote a single language.

They are *very* different.

Also C# array are declared as a type rather than
type/context:

e.g. int[] x; v.s. int x[];

C# has the advantage of practical "non-rushed" thinking in its
design.

I have the highest regards for Anders Hejlsberg, but believe he
designed a Java killer with the best from Delphi, not a C++
replacement.

http://msdn.microsoft.com/vcsharp/homepageheadlines/hejlsberg/default.aspx

Again. I don't deny that C++ has its place and can have advantages.
However,
I think C# is the "general" replacement for C++. People may not
fully realize
it yet. That is my opinion.

Ok, then count me in with the "People".


Bo Persson

 

[Guest]

std::vector<int> x;

std::vector<int> x;

vs.

int[] x;

I rest my case