A Call to Kill VB

I’ve been around the software development industry a few years, starting originally in Classic ASP using VBScript, then changing over to .Net around the time it first made it’s debut. It was a natural change to upgrade my skills to VB.Net – well, because that’s what it was created for, right? Not just for developers, but for enterprises to have a clear upgrade path to the current technology for existing applications, and to be able to leverage as much as possible the existing skill-set within the organization.

Here we are, ten years later. VB.Net, why do you still exist?

After years of VB.Net getting the language feature Me-Too! treatment, it’s still out there. I’m still seeing developers clinging to this antiquated language with a firm death grip. And I’m still seeing new projects being started with VB.Net…

I realize that .Net was architected with many different languages in mind – so that there would be peace, love and harmony between all developers (except Java!), but is VB even relevant anymore? In fact, whenever someone talks about a .Net application, or working with .Net, I only assume C#. With VB.Net’s ancient syntax, it feels like a “programming for dummies” project that’s gone too far. It’s almost condescending every time I have to code… Staring back at me all smug – saying “you don’t know what you’re doing! Why are you even getting paid?!” OK that part is in my head, but it’s still a WTF feeling…

On the Microsoft side of things; when Microsoft releases new versions of the framework, like Silverlight for Windows Phone, or XNA, C# gets first class treatment, then a VB.Net version is hacked into existence. It’s obvious who’s the star of the show in their eyes when it come to .Net, so who are we kidding? Is VB’s existence even justified anymore? .Net toolsets have matured to the point where Microsoft could, and should be including an uprade wizard to go from a VB.Net project to a C# project. Why not?!

When a development team brings on a new hire based on .Net development skills, 9 out of 10 times they will stare in shock at the existence of VB.Net apps in an Enterprise suite, and have that look of disbelief that some of those apps are brand new.

Microsoft, isn’t it about time you put a bullet in this lame dog? It’s called progress – let’s stop clinging to the past and euthanize VB for the betterment of mankind.


5 Responses to A Call to Kill VB

  1. Rob Janes says:

    Going good, graduated from Paramedic Academy in July of last year, just moved home to Nova Scotia after spending the last 6 months in Labrador as a Medic there. Brrr.

    Not much else new, all told.

    How are things up your way, a lot has changed by the looks of things! I have yet to meet your new squeeze haha

  2. Rob Janes says:

    Truer words hath not been spoken.

    However, in retrospect before the .NET Framework, Visual Basic 6 was a god-send. Now, it’s the bastard ginger child.


    Cousin Rob!

  3. Completely agree, some keep dreaming of better days though… How’s it going Cousin Rob? :)

  4. Ross Rydman says:

    I remember thinking Visual Basic was soooo cool because I could lay out controls on the screen without writing any code. That was way back in like Middle school haha.

    In the grand scheme of things however, there are far worse things in the enterprise that need to be depreciated long before anyone gets down to Visual Basic on the list. I’m looking at you AS/400…

  5. Well, I don’t think the Microsoft .Net development group has any control over a single AS/400 running in a back-office somewhere, so my call on MS to destroy VB still stands. I can only ask they change the things they can control, and VB is well within their domain.

%d bloggers like this: