RCS said:
There is a much bigger issue with the VB.NET vs C# war - and that is with
finding answers to problems -or- learning how to do something. On the
newsgroups and many websites - there are FAR more examples in C#, than
VB.NET - I suspect because VB.NET developers are typically not the types to
go into deeper subject matter. They are the "crank out a working
application" type of developers.
Or maybe, we can work out the answers more frequently by ourselves
For example, I was working on making my own validator (inheriting from
BaseValidator) - and I found next to no examples in VB - everything was in
C#. And likewise, *all* of the VB.NET developers I know - would've just
"done it another way", rather than create their own validator (which now
works great, by the way!)
Well, I've created validators. I've created HttpModules and
HttpHandlers. Yes, a lot of code samples are in C#. But it's not like
translating is difficult. Step one, copy. Step two, paste. Step three,
hit compile. Start fixing the errors. Snot difficult. (In fact, this is
the way I've taught myself some languages - with the compilers errors
and the online help).
[snip]
It will make you a more valuable developer to be solid in both languages.
Indeed. The framework itself is the largest part of learning either of
these languages coming from an older language. And the framework is
common between them. I use C# in the following circumstances: 1) When I
want to do unsafe code, 2) When I want to knock
off^H^H^H^H^H^H^H^H^Hreuse a large amount of code from elsewhere, or 3)
When I think I might be getting a bit rusty in C#.
I think in large part it depends on your own background, what the
standards are for the company you work in, and how much either of the
two languages "speaks to you". I've heard about as many people claim
that they find the syntax for VB is easier than C# as I have heard it
stated the other way around.
Damien