10 Reasons Why Visual Basic is Better Than C#
-
To add to the above: 1) Case is case - and people use it for different things. Personnaly, I like case to be maintained as it ensures camelCase it not lost halfway through - and since Intellisense sorts it out for you, it is hardly a problem. 2) I will give them that one - but the case statement is not meant for things like that: if statements are. 3) Is it so much work to do this? Rename works to re-assign the handler in C# anyway... 4) If you can't work out symbols for operators, perhaps you would be better off with COBOL... 5) I prefer the C# snippet "prop":
prop[TAB][TAB]
public int MyProperty { get; set; }
Ready to be filled in... 6) Char.IsNumber anyone? 7) For the same reason that most languages have a full stop at the end of the sentence. 8) Doctor Jones, anyone? Professor Plum? Constable Smith? Mr White? Mrs Black? 9) Strictness is a virtue of C# not a problem - hence the existance of type safe List<T> rather than ArrayList 10) And what do you think ReDim Preserve is doing behind the scenes? At least with the C# version it is obvious that this is going to consume time and memory... IMHO Andy Brown needs to get a bit more real-world experience before shooting his keyboard off...
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
For 2. he says that "It’s easy to forget to type in each of these Break statements!" conveniently ignoring that C# Compiler gives you an error saying that Control cannot fall through from one case label to another...
A year spent in artificial intelligence is enough to make one believe in God
-
- type casting: one can save a pair of parentheses, compared to C#.
And just think of the saving in wear and tear on the '[' and ']' keys! :laugh:
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
Fully agree, I more had the impression: 10 reasons why this guy doesn't know sh*t and I wouldn't like to have him on my team. :-D
V.
Totally agreed.
-
Here[^] Now, where was that bulletproof vest? <Takes cover under a fireproof blanket> A bulletproof vest can take at least one 45ACP, right?
Light moves faster than sound. That is why some people appear bright, until you hear them speak. List of common misconceptions
I'm really surprised no one else caught this, but his example of "stupid symbols" is incorrect.
C# VB.NetTest if two conditions are both true && and
Test if one or other condition is true || orThe C# equivalent of "And" is "&", and the the VB.Net equivalent of "&&" is "AndAlso". For a guy who's worried about how often he's going to have to hit the shift key, I'd think he'd prefer these quick symbols to the verbosity of VB.
-
Yes! "I am rarely happier than when spending entire day programming my computer to perform automatically a task that it would otherwise take me a good ten seconds to do by hand." - Douglas Adams
-
Actually, they aren't the same. VB.net was created with backwards compatibility with VB 6.0, with in mind, some ugly things happens (some of these VB programmers like), like the automatic type conversion, the rounding of integers, the internal VB functions, and the list goes long. The first version of .net, come in times when the Java are becoming popular between desktops and Delphi are going to be the most used language to desktop programming. Microsoft created "a plus" for the VB 6 programmers and introduced its brand new language, the C#. As a experienced VB.net and C# programmer (and ok, Delphi too), I rather say that VB is one of the worst languages I know. His apparently easy syntax do any people think they can develop, and almost all programmers that use VB.net as his primary languages aren't good programmers at all. This is my opinions, you can start offending my mother now. :D
-
Here[^] Now, where was that bulletproof vest? <Takes cover under a fireproof blanket> A bulletproof vest can take at least one 45ACP, right?
Light moves faster than sound. That is why some people appear bright, until you hear them speak. List of common misconceptions
That's normal that C# developers thinks that VB is s*it.. it is like C/C++ and C#... C# developers thinks to be cool just because there is a "C" char in the name....
-
- type casting: one can save a pair of parentheses, compared to C#.
VB has a very useful typecasting.
Dim num As Integer = "one"
Very useful. Any VB programmer who thinks it can criticizes any other language, MUST use Option Strict.
-
Here[^] Now, where was that bulletproof vest? <Takes cover under a fireproof blanket> A bulletproof vest can take at least one 45ACP, right?
Light moves faster than sound. That is why some people appear bright, until you hear them speak. List of common misconceptions
I can write both languages equally. I just hate the snobbery that is displayed by some C# programmers. The differences between the languages is getting slimmer with every version. As I see it C# is much nearer to VB.Net than it is to C. There are many things that were in VB long before they appeared in C#. The article is right, the Visual Studio IDE recompile on the fly and show syntax errors faster in VB than it does in C#. This is not about the language but it can be taken into account when you choose a language. This days I work mainly in C# and I enjoy it. The one thing I miss is the ability to put a property in a ref our out parameter. VB can do that and C# (at least 3.5) can't.
-
Here[^] Now, where was that bulletproof vest? <Takes cover under a fireproof blanket> A bulletproof vest can take at least one 45ACP, right?
Light moves faster than sound. That is why some people appear bright, until you hear them speak. List of common misconceptions
-
VB has a very useful typecasting.
Dim num As Integer = "one"
Very useful. Any VB programmer who thinks it can criticizes any other language, MUST use Option Strict.
Anything is more useful than the (type)object of C# beyond the most basic typecasting. Delphi's type(object) and VB's CType(object,type) leaves us something that can be followed by a dot at least.
-
Actually, they aren't the same. VB.net was created with backwards compatibility with VB 6.0, with in mind, some ugly things happens (some of these VB programmers like), like the automatic type conversion, the rounding of integers, the internal VB functions, and the list goes long. The first version of .net, come in times when the Java are becoming popular between desktops and Delphi are going to be the most used language to desktop programming. Microsoft created "a plus" for the VB 6 programmers and introduced its brand new language, the C#. As a experienced VB.net and C# programmer (and ok, Delphi too), I rather say that VB is one of the worst languages I know. His apparently easy syntax do any people think they can develop, and almost all programmers that use VB.net as his primary languages aren't good programmers at all. This is my opinions, you can start offending my mother now. :D
sergio_ykz wrote:
VB.net was created with backwards compatibility with VB 6.0
Nope. That's not true (at least in my opinion).
sergio_ykz wrote:
This is my opinions, you can start offending my mother now.
I balanced the silly
1you got.Veni, vidi, vici.
-
I really don't understand the C# vs VB antagonism. If you're a professional programmer, you should be able to code in both languages with same ease. When C# people roar out against VB, they're being plain childish. As are the VB people when they claim that they don't understand C#.... I code in both languages and like them both!
Why can't I be applicable like John? - Me, April 2011
-----
Beidh ceol, caint agus craic againn - Seán Bán Breathnach
-----
Da mihi sis crustum Etruscum cum omnibus in eo!
-----
Just because a thing is new don’t mean that it’s better - Will Rogers, September 4, 1932Johnny J. wrote:
If you're a professional programmer, you should be able to code in both languages with same ease.
Why? While they both target the same CLR, the syntax of the two languages is sufficiently different that while you may be able to code in one fluently, you might find the other more complicated. This has nothing to do with being a professional programmer. I don't dislike VB.NET, nor do I particularly like it. I am ambivalent towards it - if it had never been created, I wouldn't have felt the need to bemoan it; but similarly I don't feel the need to bemoan its existence. As my background is C/C++, the syntax of C# feels more natural to me, but I fully appreciate that it feels alien to a VB.NET programmer. That doesn't mean they aren't of the same standard as me, it just means they are familiar with a different syntax.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility
-
Anything is more useful than the (type)object of C# beyond the most basic typecasting. Delphi's type(object) and VB's CType(object,type) leaves us something that can be followed by a dot at least.
s = ((string) o).Trim() -
Here[^] Now, where was that bulletproof vest? <Takes cover under a fireproof blanket> A bulletproof vest can take at least one 45ACP, right?
Light moves faster than sound. That is why some people appear bright, until you hear them speak. List of common misconceptions
The last reason, involving extending arrays, shouldn't be relevant. If you're wasting time extending arrays instead of manipulating a generic list, and then calling List.ToArray() (or List(of T).ToArray() if you insist on VB) when you're done manipulating the collection's contents and need to return the array, then you're probably doing it wrong.
When posting here, I do not represent anybody but myself.
-
It seems to me that C# devs should be getting on with coding instead of spending their time moaning about us VB guys. At the end of the day its the front end that matters to a customer.
Mine is not to reason why. Mine is just to code and cry. http://www.skillsmaster.co.uk
What really matters is getting paid. If I get paid the same amount per hour either way to use C# or VB, then I'll keep my preferences (C#) to myself and give the client his money's worth.
When posting here, I do not represent anybody but myself.
-
I love VB as a language. I also completely agree with the IntelliSense thing... C# IntelliSense is a disaster if you're used to VB. For example: Typing VB: Dim ex As ExcepR... Oops, backspace, tab and it's there. Typing C#: ExcepR... Oops, backspace, no IntelliSense window pops up, either four times backspace or Shift + Home + Delete/Backspace. If you're lucky you don't have to switch to a new line to get IntelliSense support again! This becomes really very frustrating when you got code like obj.Property1.Property2.Property3... However, one reason NOT to use VB...
Form1.Text = "What the? Since when is Text a Shared/static Property!?"
The answer to that question is: Since VB1. And it's still there for 'backwards compatibility' (the compiler does create an instance though) :) So much for Object Orientism. Another one is the default of Option Strict Off. I've seen 'modern' VB code that used the horrible Form1.Text thing and Option Strict Off... You'll never see that in C#. Of course bad code can be written in both languages and with that philosophy in mind I don't really care which language I write. I just slightly prefer VB for IntelliSense and Event Handling in WinForms (that guy is so right about that!) :)
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
}I spent a year doing VB.net in Visual Studio and the Intellisense/autocomplete drove me nuts -- it kept deleting stuff I'd already typed. :mad: It never does that with C#.
-
Here[^] Now, where was that bulletproof vest? <Takes cover under a fireproof blanket> A bulletproof vest can take at least one 45ACP, right?
Light moves faster than sound. That is why some people appear bright, until you hear them speak. List of common misconceptions
Jörgen Andersson wrote:
Now, where was that bulletproof vest?
I don't think that will be enough. You may consider moving to a deep bunker. About the article: 1 - Of those 10 reasons, mostly are unfounded and gives a pretty good impression that the author is very inexperienced on the subject he's writing about. 2 - For the same reason above, I get goose bumps when I inherit VB.Net code from a VB.Net developer. Not that VB.Net developers are inherently inexperienced, but I see far more bad VB.Net code than bad C# code. 3 - I'd say there are a hundred reasons why C# is better than VB.Net.
"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson "Our heads are round so our thoughts can change direction." ― Francis Picabia
-
s = ((string) o).Trim()There are the extra parentheses mentioned by me above.
-
I sincerely hope checked and the article is satire. If it isn't, the guy's I wrote the following because I'm an idiot: 1. Writing software well is a matter of attention to details. If you can't be arsed to even get the name of something right, you're probably going to screw up more important things. 2. If you're going to criticize a language, at least get your examples right. His C# code doesn't duplicate the logic in his VB. 3. Learn how your IDE works, moron. I can assign events in my C# code any time I like, and I'm using VS2008. 4. These are operators, which I would expect to be concise. Can you imagine writing this:
proportion = openquantity openquantity a addto b addto c addto d closequantity dividedby e closequantity multipliedby 100
instead of
proportion = ((a + b + c + d) / e) * 100
Secondly, programming is symbol manipulation. As in my response to #1, if you can't get this right, there are a whole bunch of other things you won't get right. 5. Sigh. Snippets in the IDE. The guy's like a carpenter who has to be told how to use a hammer every morning. 6. They's in the bloody CLR library. In 30 years of programming, not once have I needed to use the mortgage payment function. As far as 'is number' goes, I do localized applications. The library functions for validating localized numbers are usually inept. The .NET versions are actually pretty good, from what I've seen. They seem to work well for common number formats found in the U.S., Europe, and Asia. 7. VB's line continuation character is as annoying as Pascal's use of the semicolon as a statement separator. It's a special case you have to remember all of the time. At least with the C-style languages, you just put the semicolon at the end of every statement. Period. 8. To-may-toe, To-mah-toe. 9. VB encourages you to be sloppy. Once again, point #1. 10. C# gives you a whole lot more control over data structure transformations. With a language that encourages sloppiness, I wouldn't expect it to handle this kind of thing in a fashion that performed well.
Software Zen:
delete this;Gary Wheeler wrote:
you just put the semicolon at the end of every statement. Period.
Even after a compound statement? :-D
