Oops, 7 Days. Hey look I don't update on weekends.

Why so much VB on MSDN?

http://blogs.msdn.com/tomarcher/comments/495282.aspx

Hmmm. VB'ers, damn you all, won't read an article with C# or C++, but us open-minded C#/++ types will read an article in VB. WTF! So now I get punished for being progressive?! Yeah yeah, the languages are similar. But dammit, I am a copy/paster.
Permalink sharkfish 
January 5th, 2006
It takes, like, a minute to convert VB to C#. I don't understand what you're complaining about.
Permalink sixtyten 
January 5th, 2006
Have you seen VB? It's ugly. Yeah, I translate all the time. But it is ANNOYING. I bought the horse M$ sold, and now they are all like "yeah well, we're gonna cater to VB'ers".

I am just a little insulted.
Permalink sharkfish 
January 5th, 2006
Why do I relate everything these days to the following:

(1) Good programmers (those who're constantly trying to better themselves) vs. bad programmers (those that code to pay the bills);
(2) The importance of knowing low-level stuff; and
(3) How do you hire or spot the good programmer


The whole division of VB vs. this and that is a business perception. The division exists because there are two different markets. The mindsets of a typical "VB only" (emphasising on "only") is different from the C/C++/C# programmer.

However, the good programmer is beyond languages. They love one language and are agnostic to the rest of the whole world of programming languages.
Permalink Sathyaish Chakravarthy 
January 5th, 2006
I'm with Sharkfish on this one. I've had to, well...."deal" with VB-based projects before. Simply put, it's crap.

Although I'm not one of those zealouts who are somehow married to a particular language, but I will simply avoid VB because there are better languages out there. However, if all you're doing is something incredibly simple and stupid such that VB is the quickest way to get something done, then go for it.

Thankfully I've never been forced to use it.
Permalink QADude 
January 5th, 2006
I'm a big fan of VB -- been programming in Microsoft basic in one form or another my entire life. That being said, I see no reason for VB.NET to exist. It simply complicates matters for no good reason.

VB6 should have been ported to .NET in a 100% compatible way and used to migrate old projects to the platform. There's no reason why a classic VB programmer couldn't migrate to C# -- there's no need for this bastardized VB to exist.
Permalink Almost H. Anonymous 
January 5th, 2006
The only reason I prefer VB.NET to C# is that it seems to work better with the IDE, the intellisense, and auto formatting, etc, all plays a lot nicer with VB.NET, and thus the development experience is speedier.
Permalink Phil 
January 5th, 2006
Personally, I find VB.NET to be more easily readable than C#.

And considering that most of my software projects will be put away for two to six months before being picked up again, that's a good enough reason for me.
Permalink Steve Barbour 
January 5th, 2006
IronPython is also coming soon. That might be interesting...
Permalink Jeff Barton 
January 5th, 2006
" Personally, I find VB.NET to be more easily readable than C#."

No. Brackets are better than "IF...END IF". ;p
Permalink sharkfish 
January 5th, 2006
(1) Because the poor VB.NET people bitch about having to read C#, while the C# people are perfectly happy to read VB.

(2) Because they need the additional help. ;-)
Permalink example 
January 5th, 2006
I think example nailed it on the head with #2.
Permalink SomeBody 
January 5th, 2006
Hey! Although there are probably more bad VB programmers than, say, C++ programmers, this is purely because anyone with a copy of Word can become a VB "programmer". There's nothing inherently wrong with VB, though, and in the hands of someone who knows what they're doing it's just as good as C#, and it has the advantage of being easier to follow without knowing the specifics and so is ideally suited for sample code.
Permalink Mat Hall 
January 6th, 2006
I'll take all the help I can get. :P
Permalink Steve Barbour 
January 6th, 2006
I can say #2 because I was a VB programmer for many years.

Part of the culture of VB programming is a attitude of "just make it work". The VB programmers who paid attention to proper design and stuff like data structures were few and far between. So, you have people who use CS skills in the design of their programs, and this other vast population of people who don't. As a result, the help files are geared towards the larger population.
Permalink example 
January 6th, 2006
There has been a concerted effort for the past 3 or so years by the Visual Basic Microsoft MVPs to get more VB content out there on MSDN and the like. What you're seeing is a result of that effort.
Permalink Jacob 
January 6th, 2006

This topic was orginally posted to the off-topic forum of the
Joel on Software discussion board.

Other topics: January, 2006 Other topics: January, 2006 Recent topics Recent topics