R
RobinS
Jon Skeet said:I'd love to know more about how these figures break down. I suspect
there are plenty of people who develop software as *part* of their jobs
who use VB, but I suspect that if you restricted the survey to those
who are full-time developers, the story would be significantly
different.
Do you mean you think the numbers would be much lower?
I'd like to know where they *got* those figures, because I certainly
haven't seen it reflected in the job market in the SF Bay Area.
I suspect there are many people like my father, who put
together VB programs as part of a job which would never normally be
called a development role, but who would count himself as a VB
developer. I suspect things would also change if you looked at people
developing "shrink-wrap" applications vs those developing "in-house"
business applications.
Do you suspect "shink-wrap" are done in C#, and in-house are in VB? That
would be my expectation.
Now, my paragraph above was mostly thinking of VB6, rather than VB.NET.
My guess (and all of these suggestions are just guesses and suspicions)
is that VB.NET has made more of an impact on the full-time developer
than VB6 did - although it would be interesting to see how many people
went from, say, Java to VB.NET compared with those going from VB6 to
C#. (I've heard of various people doing the latter, but none doing the
former. I'm sure they exist, I just haven't heard about them.)
I think there was a lot of VB6 usage by people writing in-house business
apps for small divisions. That's what my last two jobs were. The apps are
still running, and there is no interest in converting them to .Net because
they run just fine. It was easier for people to take up VB6 than VB.Net, so
I think there are a lot more "fly by the seat of your pants" applications
written in VB6 than anybody knows of.
None of this prevents VB.NET from being a perfectly viable language, of
course. I happen to prefer C# in various ways, but that's a different
matter.
I use whichever one has the most interesting job, and there seem to be more
interesting jobs with C#, so that's the way I'm going these days. But I
like VB, too.
Robin S.