Your analogy is still flawed. A better analogy is to say I prefer using an
electric saw to build a house instead of a handsaw because using an
electic saw is faster. That is perfectly valid and I still end up with a
house in the end, just faster and possibly a better quality house (due to
the fact that my saw has better compiler checks and is a stricter saw).
Assuming your saw in this case is C#, perhaps you could enlighten us as to
how it's:
a) Faster
b) Likely to produce a better quality end result, seeing as how both
languages boil down to virtually identical IL
c) Has better compiler checks and is stricter
There is no performance difference between the two languages, and this point
has been re-hashed here so many times that it's starting to get very
tiresome. The only advantage C# has in performance terms is when you start
to use unmanaged code, which VB can do through the use of the Marshal class
anyway with a small performance penalty. The only people I've heard enquire
about switching to C# because it "produces faster code" were total .NET
newbies who didn't know their strongly typed arses from their elbows.
If you really want the analogy to work, then I believe this is the most
accurate:
We both build wood houses. You prefer your Black & Decker electric saw, I
prefer my DeWalt electric saw. You can take the safety guard off your saw
whereas I cannot on mine - big wow, I've only ever needed to do that once or
maybe twice in all the houses I've built. The grip on my saw is better, the
battery display on your saw is nicer, but in the end they both produce an
identical wooden house and it takes each of us the same time to reach that
result because we're both using the saws we feel most comfortable and
familiar with.
The real difference between the two saws? I don't mind using the Black &
Decker every once in a while, whereas you whinge about the DeWalt even when
you *don't* use it. This is of course not a slam on the B&D saw - just a
slam on some of the people that use it.
