<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: C++ vs. C# - a Checklist from a C++ Programmers Point of View</title>
	<atom:link href="http://www.thinkingparallel.com/2007/03/06/c-vs-c-a-checklist-from-a-c-programmers-point-of-view/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thinkingparallel.com/2007/03/06/c-vs-c-a-checklist-from-a-c-programmers-point-of-view/</link>
	<description>A Blog on Parallel Programming and Concurrency by Michael Suess</description>
	<pubDate>Wed, 19 Jun 2013 12:48:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Isaac T</title>
		<link>http://www.thinkingparallel.com/2007/03/06/c-vs-c-a-checklist-from-a-c-programmers-point-of-view/comment-page-3/#comment-98949</link>
		<dc:creator>Isaac T</dc:creator>
		<pubDate>Sun, 06 May 2012 03:27:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkingparallel.com/2007/03/06/c-vs-c-a-checklist-from-a-c-programmers-point-of-view/#comment-98949</guid>
		<description>I am a C# programmer and am currently teaching myself C++. I haven't read all the comments so forgive me if I retread over something already stated. Your choice of programming languages deal more with what you plan to program, not simple pros and cons. If you want to create high perfomance graphics programs for Windows, I recommend C++, If you are creating non-graphics intensive applications C# is great. Learn Java, HTML, or XAML for web.

I learned C# in college. I am learning C++ so I can program DirectX-based apllications. The platform for which you want to program is far more important than a few pros and cons.</description>
		<content:encoded><![CDATA[<p>I am a C# programmer and am currently teaching myself C++. I haven&#8217;t read all the comments so forgive me if I retread over something already stated. Your choice of programming languages deal more with what you plan to program, not simple pros and cons. If you want to create high perfomance graphics programs for Windows, I recommend C++, If you are creating non-graphics intensive applications C# is great. Learn Java, HTML, or XAML for web.</p>
<p>I learned C# in college. I am learning C++ so I can program DirectX-based apllications. The platform for which you want to program is far more important than a few pros and cons.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rhonald Moses</title>
		<link>http://www.thinkingparallel.com/2007/03/06/c-vs-c-a-checklist-from-a-c-programmers-point-of-view/comment-page-3/#comment-98942</link>
		<dc:creator>Rhonald Moses</dc:creator>
		<pubDate>Sun, 01 Apr 2012 04:35:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkingparallel.com/2007/03/06/c-vs-c-a-checklist-from-a-c-programmers-point-of-view/#comment-98942</guid>
		<description>To begin with: Congrats! this thread is 6 years old and still active  :grin: 

Again, it's what you want to do comes first and then comes what you want to use to get what you want, then the third, how good are you with what you want to use to get what you want.

So, even if you want hardware level interaction, but you are good with C# than C++ (let's agree, most of the guys haven't used C++ except for colleges), try to figure our what are the libraries that supports the level of programming you want (unsafe namespace with pointers inside for example).

If you are well versed with C++ (or willing to spend some time to learn it), then I'd suggest you to go for C++.

Again, it's what you want, with what you want and how comfortable are you with what you want to use to get what you want.

 :mrgreen:</description>
		<content:encoded><![CDATA[<p>To begin with: Congrats! this thread is 6 years old and still active  <img src='http://www.thinkingparallel.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':grin:' class='wp-smiley' /> </p>
<p>Again, it&#8217;s what you want to do comes first and then comes what you want to use to get what you want, then the third, how good are you with what you want to use to get what you want.</p>
<p>So, even if you want hardware level interaction, but you are good with C# than C++ (let&#8217;s agree, most of the guys haven&#8217;t used C++ except for colleges), try to figure our what are the libraries that supports the level of programming you want (unsafe namespace with pointers inside for example).</p>
<p>If you are well versed with C++ (or willing to spend some time to learn it), then I&#8217;d suggest you to go for C++.</p>
<p>Again, it&#8217;s what you want, with what you want and how comfortable are you with what you want to use to get what you want.</p>
<p> <img src='http://www.thinkingparallel.com/wp-includes/images/smilies/icon_mrgreen.gif' alt=':mrgreen:' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://www.thinkingparallel.com/2007/03/06/c-vs-c-a-checklist-from-a-c-programmers-point-of-view/comment-page-3/#comment-98941</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Sun, 01 Apr 2012 04:33:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkingparallel.com/2007/03/06/c-vs-c-a-checklist-from-a-c-programmers-point-of-view/#comment-98941</guid>
		<description>RedCopper: I agree, it doesn't really make much sense to say something like "Real programmers use C++", as we should really just use the best tool for the job.

Over time, I've started to feel like these "language 1 vs. language 2" threads are bait for a flame war more than anything.</description>
		<content:encoded><![CDATA[<p>RedCopper: I agree, it doesn&#8217;t really make much sense to say something like &#8220;Real programmers use C++&#8221;, as we should really just use the best tool for the job.</p>
<p>Over time, I&#8217;ve started to feel like these &#8220;language 1 vs. language 2&#8243; threads are bait for a flame war more than anything.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RedCopper</title>
		<link>http://www.thinkingparallel.com/2007/03/06/c-vs-c-a-checklist-from-a-c-programmers-point-of-view/comment-page-3/#comment-98940</link>
		<dc:creator>RedCopper</dc:creator>
		<pubDate>Sun, 01 Apr 2012 03:27:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkingparallel.com/2007/03/06/c-vs-c-a-checklist-from-a-c-programmers-point-of-view/#comment-98940</guid>
		<description>Lot of arrogance here with the "real programmers use C++" attitude.  I'm surprised those who deride C# for having hand-holding training wheels, don't realize that that's the whole point of high-level languages: To make things simpler for the programmer. Well I think people who program in C++ are lazy tyros who need a crutch, as real men program with front panel toggle switches. :roll: 

In the real world, the importance of sheer runtime performance (or more accurately, efficiency) isn't as important as it once was.  The computer spends nearly all its cycles waiting for the user or other hardware to do something.  If the user does something and it takes C++ 2ms to complete and C# does the task at an agonizingly slow 3ms, is that an acceptable trade-off if you can get the C# app to market significantly faster?

Of course, there are plenty of cases where ultimate performance matters.  There's apparently lots of programmers, at least posting here, who write full blown commercial games and operating systems.  They shouldn't even touch C#.   It's neither intended, not is it appropriate for those.   For most of us, performance needs to be weighed against other factors:  Time to develop; time to test and debug; stability; compatibility; maintainability... Then, and only then, does a good programmer decide which language is "best".   But I guess if all you have is a hammer++...

And I suspect everyone championing creative, more that one way to do it, outside the box power programming have never been tasked with maintaining a b'zillion lines of code written by a creative, more than one way to do it, outside the box power programmer.</description>
		<content:encoded><![CDATA[<p>Lot of arrogance here with the &#8220;real programmers use C++&#8221; attitude.  I&#8217;m surprised those who deride C# for having hand-holding training wheels, don&#8217;t realize that that&#8217;s the whole point of high-level languages: To make things simpler for the programmer. Well I think people who program in C++ are lazy tyros who need a crutch, as real men program with front panel toggle switches. <img src='http://www.thinkingparallel.com/wp-includes/images/smilies/icon_rolleyes.gif' alt=':roll:' class='wp-smiley' /> </p>
<p>In the real world, the importance of sheer runtime performance (or more accurately, efficiency) isn&#8217;t as important as it once was.  The computer spends nearly all its cycles waiting for the user or other hardware to do something.  If the user does something and it takes C++ 2ms to complete and C# does the task at an agonizingly slow 3ms, is that an acceptable trade-off if you can get the C# app to market significantly faster?</p>
<p>Of course, there are plenty of cases where ultimate performance matters.  There&#8217;s apparently lots of programmers, at least posting here, who write full blown commercial games and operating systems.  They shouldn&#8217;t even touch C#.   It&#8217;s neither intended, not is it appropriate for those.   For most of us, performance needs to be weighed against other factors:  Time to develop; time to test and debug; stability; compatibility; maintainability&#8230; Then, and only then, does a good programmer decide which language is &#8220;best&#8221;.   But I guess if all you have is a hammer++&#8230;</p>
<p>And I suspect everyone championing creative, more that one way to do it, outside the box power programming have never been tasked with maintaining a b&#8217;zillion lines of code written by a creative, more than one way to do it, outside the box power programmer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: elmo</title>
		<link>http://www.thinkingparallel.com/2007/03/06/c-vs-c-a-checklist-from-a-c-programmers-point-of-view/comment-page-3/#comment-98934</link>
		<dc:creator>elmo</dc:creator>
		<pubDate>Fri, 09 Mar 2012 11:38:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkingparallel.com/2007/03/06/c-vs-c-a-checklist-from-a-c-programmers-point-of-view/#comment-98934</guid>
		<description>....but since everyone and their grandmother seems to use Java or C# these days....


:sad:  it hurts me a lot even grandmothers seems to use these languages still I know nothing about them.  :cry:  :cry: 
 :???:  from where should I start?</description>
		<content:encoded><![CDATA[<p>&#8230;.but since everyone and their grandmother seems to use Java or C# these days&#8230;.</p>
<p> <img src='http://www.thinkingparallel.com/wp-includes/images/smilies/icon_sad.gif' alt=':sad:' class='wp-smiley' />  it hurts me a lot even grandmothers seems to use these languages still I know nothing about them.  <img src='http://www.thinkingparallel.com/wp-includes/images/smilies/icon_cry.gif' alt=':cry:' class='wp-smiley' />  <img src='http://www.thinkingparallel.com/wp-includes/images/smilies/icon_cry.gif' alt=':cry:' class='wp-smiley' /><br />
 <img src='http://www.thinkingparallel.com/wp-includes/images/smilies/icon_confused.gif' alt=':???:' class='wp-smiley' />  from where should I start?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexander Alvonellos</title>
		<link>http://www.thinkingparallel.com/2007/03/06/c-vs-c-a-checklist-from-a-c-programmers-point-of-view/comment-page-3/#comment-98929</link>
		<dc:creator>Alexander Alvonellos</dc:creator>
		<pubDate>Thu, 01 Mar 2012 21:34:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkingparallel.com/2007/03/06/c-vs-c-a-checklist-from-a-c-programmers-point-of-view/#comment-98929</guid>
		<description>If you're going to talk about parallelism and concurrency, you need to be demonstrating it in Ada. That's the bottom line. When you get into pthreads and the multithreading models that are so involved in C/C++, you're also tying yourself to operating system dependence. It's really easy to get lost in senseless coding. The problem with teaching concurrency in a byte code compiled language like Java or C# is that you get too far away from the OS and off into this magical wonderlands of objects. Ada is a happy medium between the two of them. Ada's syntax, library, compiler (GNAT), and type checking system is delectable. Try it.</description>
		<content:encoded><![CDATA[<p>If you&#8217;re going to talk about parallelism and concurrency, you need to be demonstrating it in Ada. That&#8217;s the bottom line. When you get into pthreads and the multithreading models that are so involved in C/C++, you&#8217;re also tying yourself to operating system dependence. It&#8217;s really easy to get lost in senseless coding. The problem with teaching concurrency in a byte code compiled language like Java or C# is that you get too far away from the OS and off into this magical wonderlands of objects. Ada is a happy medium between the two of them. Ada&#8217;s syntax, library, compiler (GNAT), and type checking system is delectable. Try it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://www.thinkingparallel.com/2007/03/06/c-vs-c-a-checklist-from-a-c-programmers-point-of-view/comment-page-3/#comment-98923</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Wed, 01 Feb 2012 15:35:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkingparallel.com/2007/03/06/c-vs-c-a-checklist-from-a-c-programmers-point-of-view/#comment-98923</guid>
		<description>C++ is not limited to 32 bits.  Some compilers (such as Microsoft Visual Studio) can compile 64-bit binaries with C++ and have been able to do so for years already.</description>
		<content:encoded><![CDATA[<p>C++ is not limited to 32 bits.  Some compilers (such as Microsoft Visual Studio) can compile 64-bit binaries with C++ and have been able to do so for years already.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JB</title>
		<link>http://www.thinkingparallel.com/2007/03/06/c-vs-c-a-checklist-from-a-c-programmers-point-of-view/comment-page-3/#comment-98922</link>
		<dc:creator>JB</dc:creator>
		<pubDate>Wed, 01 Feb 2012 10:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkingparallel.com/2007/03/06/c-vs-c-a-checklist-from-a-c-programmers-point-of-view/#comment-98922</guid>
		<description>But, yes. Originally C++ was created with 32 bit in mind, However not without some predictions that we will one day evolve to higher Bitrates. 64, 128, 256, etc... as the basic premise will be the same many variables will be recreated to accomodate for better systems. 

I know I am not helping, but I am bouncing my thoughts off your questions to absorb /learn , disect, analyze and interpret for the sake of my learning curve. Thanks for raising that question LOCNK!

~JB</description>
		<content:encoded><![CDATA[<p>But, yes. Originally C++ was created with 32 bit in mind, However not without some predictions that we will one day evolve to higher Bitrates. 64, 128, 256, etc&#8230; as the basic premise will be the same many variables will be recreated to accomodate for better systems. </p>
<p>I know I am not helping, but I am bouncing my thoughts off your questions to absorb /learn , disect, analyze and interpret for the sake of my learning curve. Thanks for raising that question LOCNK!</p>
<p>~JB</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JB</title>
		<link>http://www.thinkingparallel.com/2007/03/06/c-vs-c-a-checklist-from-a-c-programmers-point-of-view/comment-page-3/#comment-98921</link>
		<dc:creator>JB</dc:creator>
		<pubDate>Wed, 01 Feb 2012 10:51:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkingparallel.com/2007/03/06/c-vs-c-a-checklist-from-a-c-programmers-point-of-view/#comment-98921</guid>
		<description>LOCNK:  Im no pro, but I believe you have to port C++ over from 32 to 64. there are a few things that will have to be done to make this migration successful. 


-JB


REFERENCE: http://www.linuxquestions.org/questions/programming-9/32-bit-to-64-bit-migration-for-c-program-613579/


and also, I believe in the course of a weekend and a few weekdays I have answered my own question i posted last week.  Learn BOTH! !!!!!   

I am still open to suggestions., 

Thanks, 

JB</description>
		<content:encoded><![CDATA[<p>LOCNK:  Im no pro, but I believe you have to port C++ over from 32 to 64. there are a few things that will have to be done to make this migration successful. </p>
<p>-JB</p>
<p>REFERENCE: <a href="http://www.linuxquestions.org/questions/programming-9/32-bit-to-64-bit-migration-for-c-program-613579/" rel="nofollow">http://www.linuxquestions.org/questions/programming-9/32-bit-to-64-bit-migration-for-c-program-613579/</a></p>
<p>and also, I believe in the course of a weekend and a few weekdays I have answered my own question i posted last week.  Learn BOTH! !!!!!   </p>
<p>I am still open to suggestions., </p>
<p>Thanks, </p>
<p>JB</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: locnk</title>
		<link>http://www.thinkingparallel.com/2007/03/06/c-vs-c-a-checklist-from-a-c-programmers-point-of-view/comment-page-3/#comment-98920</link>
		<dc:creator>locnk</dc:creator>
		<pubDate>Wed, 01 Feb 2012 10:43:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkingparallel.com/2007/03/06/c-vs-c-a-checklist-from-a-c-programmers-point-of-view/#comment-98920</guid>
		<description>In case that the program needs a huge operating memory (3~10GB), what is your suggestion, C++ or C# should be used?
As far as I understand, C++ is in 32bit whereas C# is with 64bit. Is that right?</description>
		<content:encoded><![CDATA[<p>In case that the program needs a huge operating memory (3~10GB), what is your suggestion, C++ or C# should be used?<br />
As far as I understand, C++ is in 32bit whereas C# is with 64bit. Is that right?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
