Case insensitivity isn't such a big deal as long as you only ever program in VB. That's the big risk. One nice usage of case sensitivity I've seen is to use initial lower for private variables and initial upper for public methods...
private int foo
public int Foo()
While I'm generally against embedding any sort of type information in a name. I do find the above usage of case sensitivity super handy. I can't do that VB but I can in just about any other OO language.
Bah! Gimme some more of those curly brackets and a side of semicolons, too, because I just love extra typing for formatting purposes only! VB may need line continuation characters on a few lines to readability, but miss one semicolon or curly bracket in C-anything, and you're toast.
I just love how the C-types see nothing wrong with typing an extra character for each of the tens of thousands of statements that fit reasonable on one line of code -- and are the only statements on that line of code -- rather than the handful of cases where you actually want a single stament to span multiple lines of code. It seems fundamently absurd.
I suppose I could say some of the same thing about C#.
... The crummy thing has case sensitive names so POINT != Point != point which is totally ridiculous! Why would you name two variables the same thing, but use different case? Last time I checked, Peanut Butter and peanut butter are both identical (and consequently, both delicious). Why should it be different in code?
... Statement Termination Characthers?! ARRGGGHH! Rarely do your statements span multiple lines, so why make them the rule instead of the exeception.
But honestly, why care so much about the language. Everything that can be done in C# (save operator overloading and volitle members) can be done in Basic. I happen to be more productive in Basic. I like the End If/While/Select. I dont like curly braces. One should be well versed in both instead of crying when he/she doesn't have a choice.
Case sensitivity becomes an issue once you start using characters other than plain ASCII. CLR allows Unicode identifiers and there are languages that don't have a simple one to one character case matching. That's why you want case sensitivity. It takes away the guessing about what exactly is the same identifier and what's not.
"Bah! Gimme some more of those curly brackets and a side of semicolons, too, because I just love extra typing for formatting purposes only! "
If Not _myRefMember Is Nothing Then
' some code
End If
vs.
if(!_myRefMember==null)
{
// some code
}
well.. indeed C# is a hell of a lot more typing...
Also, a nice exercise for the VB.NET lovers :)
- derive a class from DataTable
- add a member to that class and a property get/set combi
- add code to be able to serialize/deserialize your added member.
Good luck! :)
(hint: you can't do this in VB.NET, because VB.NET doesn't allow you to explicitly implement an interface again (DataTable implements ISerializable privately). You need C# for this. What a great language :))
About curlies - how exactly is {} more typing then End If? If I can count characters right it's 2 in C# versus 6 in VB. What am I missing? Same goes for ! vs. Not, null vs. Nothing, no characters vs. Then (ok, maybe two, () vs. Then), switch vs. Select Case and so on...
VB is for second class programmers and losers like you.
Folks this is a case of "Your both right" or "Your Both wrong"
or like the idea of time distrotion as you enter a black hole.... it will just go on for ever.............
I'll just point out that { or } are indeed one character each, but they need a two-keystroke combination to write.
(Oh, do ignore me. I'm just an amused observer fanning the flames a bit. :)
The most annoying things about VB.NET is its language style. Lots of texts as if u trying to be a writer instead of a programmer.
VB.NET programmers will have difficulties to join a C#, Java or C++ project (and I saw it happened to programmers)
But C# programmer will find himself comfortable in a JAVA and/or C++ project
I wonder why Microsoft does not stop from supporting this language. C# and its equivalent (Java, C++) are enough.
Guy S: boy - you're so wrong it hurts!
I'll need to talk some sense in to you in the next blogger dinner! :)
"VB is for second class programmers and losers like you."
Another reason I hate the curly-bracket languages is boorish jerks like you tend to gravitate to them.