Comments on: VB .NET or C# – The Rematch

By: A Manager’s Retrospective on the C# versus VB.NET decision « Software++

Mon, 20 Apr 2009 00:09:24 +0000

[...] members of your own team. One resource that I have come to trust over my years in this industry is Dan Appleman, who has published a highly regarded e-book, Visual Basic .NET or C#, Which to Choose? (VS2005 [...]

By: gh0st

gh0st — Fri, 13 Mar 2009 15:58:30 +0000

I disagree.

“is not is nothing” That, right there, should disqualify a language on grounds of logical speghetti.

Seriously, I am a longtime C programmer and am considering a VB position and appreciate the post. Good information.

By: Sloppy language

Sloppy language — Tue, 12 Aug 2008 19:45:12 +0000

@ Trevor.

There’s no such thing as sloppy programming language, only sloppy programmers. Programming language won’t matter if a programmer has a solid foundation.

By: Trevor

Trevor — Tue, 10 Jul 2007 02:56:10 +0000

@Thinkpad:

Not necessarily. I mean people who wrote this kind of stuffs wanted to prove something to those people who are not enlightened. I for myself is confused too before. Why VB? Why C#? Your point is quite nonsense when it comes to the legacy of programming THAT – when you came from a C/Java world, then use C# if you have experience in VB6 or BASIC 19-forgotten, the use VB.Net – YOU GOTTA BE KIDDING yourself. Are you sure what you are saying?

Here’s the point, “real developers” move from one language to other in search for tighter and perhaps more powerful language domain. I have been developing software since graduation of 98 and “was” using VB. but later, in 2002 onwards, C# caught my attention why? First, it’s not true what you have said again – that if i’m a VB person, then VB.Net for me… Wrong. C# offers a diversity of well-formulated, well-logically designed enterprise programs. You tell me, why are some critical microsoft software they are now releasing are written in C#? why not VB? Fact is, VB is qutie a sloppy language. Declare X and x, they are the same. C# is strict. And this is where logical pogram errors are trapped and handled. Error catching is tremendously implemented in C# like dead codes, etc. etc. And I don’t wanna utter more. C# has grown up on me on a solid level after the elementary grade VB. Sorry, it’s a fact.

By: Thinkpad

Thinkpad — Tue, 25 Jan 2005 14:49:40 +0000

I am actually surprised at people who write “books” on a topic such as VB.NET or C#. These people have no life!. Developers are supposed to be .NET Framework Developers not VB or C#. Dah!.. Commensense (if you have it) dictates that if you come from a C/C++, Delphi etc background you will code in C# and if you came from the antiquated VB background you will continue to use VB.NET. I made my 10 Million Dollars mark in 2004 developing rugged IP67 hand helds and selling them at half the price of symbol and intermec and provided mobility solutions on top of them. This year I will focus my energy on developing a mobility platform in .NET of course and for the religious fanatics it is coded in C#, should be ready by June and sell it at half the price of extendedsystems!. Good Luck Dan in your ventures.

By: Jeff Atwood

Jeff Atwood — Tue, 09 Nov 2004 03:10:30 +0000

Great stuff as always Dan.

A few observations..

1) Stop the presses! C# now has edit and continue– doh!

2) Is “refactoring” really a MAJOR WIN? Particularly since there are so many third party products that do this. It’s easy enough to script the IDE, and many of the third party tools are superior to the MS built-in stuff anyway..

I also agree that VB.NET is improving much more than C# in 2005. Lack of XML comments was a friggin’ disgrace in 2003.

By: rizzo

rizzo — Sat, 06 Nov 2004 22:12:36 +0000

There is also a lighter, productivity-based comparison between the 2 languages here:

Top 10 reasons VB.NET is better than C#
http://www.vbrad.com/source/src_top_10_vb.htm

Top 10 reasons C# is better than VB.NET
http://www.vbrad.com/source/src_top_10_cs.htm