| September
21st 2005
VB or C#
for .NET?
The eternal quandry
- VB 'cause plenty of people understand it or C# 'cause it's a "grown-up's"
coding language?
Presently this
project is being written in both. The worst part of this is switching
between the languages... Here, for my tuppence-worth is my assessment
of the differences:
VB |
C# |
| + Great autocomplete |
+ Brief and minimalist code |
| + Event handling without thinking |
+ XML documentation from code |
| - Continual
compile (wastes a lot of time!) (plus breaks
down a lot necessitating a rebuild) |
+ Much more
suited to OOP classes - I don't like the difference between a
function and a procedure, or the New instead of constructor |
| - .item() rather than [] |
|
| + Dim x as new thingi - neat! |
|
but at
the end of the argument - most of the code is .this.that.the_other,
calling 'stuff' from .NET and your own code, the differences are
minor in comparison to the similarities...
Given the choice
though, I'd code in C#!
|