IMHO I think Cor hit the nail on the head.
I like the VB IDE. If I had to write VB code in notepad or something like it and
compile it, I would be less inclined to use descriptive names and such. But I
really like the autocomplete, not having to worry about case, curly braces,
parenthesis, etc.
VB6 IDE made even the best C IDE I've seen pale in comparison. VB.Net IDE makes
the VB6 IDE pale, and it keeps getting better. If I had a C IDE like VB.Net a
decade ago, then I might write more C code nowadays.
I think part of the problem is that just about anyone can write something in VB
that works, but that doesn't mean it is good programming. This in general makes
C programmers look down on VB as they believe you just can't write good code in
VB.
Conversely, if you don't know anything about programming and try to pound out a
working C program, you are not going to have much luck.
But I think one of the big differences here is that most seasoned VB programmers
have spent many hours pouring over C header files to interoperate with DLL's.
Sometimes we have little choice but to employ C to overcome some of VB's
limitations. Don't hear of too many C programmers reading VB code.
C(++,#, etc) gurus tend to think C is much cleaner, easier to read, etc. This
one I just don't get.
Somehow something like:
MyClass myClass = MyClass.MyClass
(Yes, I see things like that in C# quite often. Just saw one today.)
is cleaner than something like:
Dim oMyClass as MyClass = MyClassFactory. CreateInstance( )
I just don't understand how it is CLEAR that myClass is an instance of MyClass
which is created and returned by the shared MyClass property on MyClass.
I guess it is what you know. VB is as foreign to them as C is to many VB
programmers.
Just like Mac vs. Linux vs. Windows vs. Unix, etc.
Gerald
"Cor Ligthert" <no**********@p lanet.nl> wrote in message
news:Ot******** ******@tk2msftn gp13.phx.gbl...
Hi Guy,
Stirring up trouble here;)
why is it that C# programmers try and denigrate VB.NET while VB.NET
developers seem to have no problem with C# but just prefer VB.NET? I use both and this generally seems to be the attitude, not with everyone
obviously!
Mostly because they have never used it, because C# has very much legacy C
stuff it is very easy to use for C and Java programmers. (For me it is more
the IDE from VBNet, some very handy functions and the not being of that
legacy C stuff that makes the difference in the advantage of VBNet).
However the ones who started to learn it even the most puritans C# people
talk mostly in an other way after that. Look at this page.
http://www.pobox.com/~skeet/csharp/faq/#vb.or.csharp
:-)
Cor