John,

You say VB is more efficient? Is that just for you, or do you think it's more efficient, period? Personally, I like to use C#, and for me, now that I've gotten past the syntax part of it, I think I can do things faster in C# than the equivalent thing in VB.

However, once I can get past the syntax differences for VB, I'll actually have a choice of languages: it will be a bit like being ambidextrous. I'll have effectively doubled my chances (if we assume that each language has an equal share of applications that have to be written in only that one language) for landing a particular job. (I would know how to write in 2 out of 3 languages in the .NET framework.)

Anyway, back to my point (I kind of digressed a little there), I don't think efficiency can be used as an argument for choosing one over another. If someone is more comfortable with VB-style programming, then they will be more efficient in VB.NET than in C#. However, if someone, like myself, has a hard time with the syntax of VB, they might be more comfortable and efficient in C#.

>John...
>
>This is such a crystal clear point, I don't see why some folks don't get it.
>
>In a C# windows app, if your form is named Form1, you cannot type form1 and have the intellisense work. Why? Because C# treats Form1 and form1 differently.
>
>Alot of people, including myself, use mixed case for variables, object/class names, etc. The default properties (ActiveForm, etc) are all mixed case.
>Why should I have to remember how the text is constructed? Isn't the only important element that I simply remember the name?
>
>I suppose case sensitivity has a place in certain languages. As far as being in a 4GL that is geared toward RAD and developer productivity, if I were developing the spec for such a language, I would do either of the followings:
>
>1. Eliminate case sensitivity entirely
>or
>2. Allow for the possibility of togglinh case sensitivity on and off
>
>In days gone by, when you could edit programs in a simple text editor, I can see why having to terminate lines with a semi colon, using curly braces, etc. might have been a help. As for as being able to terminate code blocks, I see nothing wrong with Sub/End Sub..
>
>Here is a good one... When you get a moment, check out the sample macros that ship with VS .NET. I thought for sure they would be written in C#. Nope... They are written in VB!!!!
>
>Having a low-level language like C# is a good thing. If you need to drop down a level for a certain reason, it is good that a language, which is not that difficult to grasp, is available to you.
>
>But, for the typical windows database app, VB will be work just fine and just as good as C#. And in return, your development efforts will be greatly enhanced because you won't have to deal with the BS idiosyncracies of C#.
>
>Is VB technically better than C#. I don't think so. From an efficiency standpoint however, VB *is* better - hands down.