Getting Stuck Into VB.NET
by Kieran- Published:May 29th, 2008
- Comments:2 Comments
- Category:Pages
I’ve taken some time out today to go over some of VB.NET’s language features and general "dialect". It’s a very odd language and seems as if it has been patched together from remnants of a shabby past. There are language features that still exist in it which are both nonsensical and medieval, for example "Sub" which doesn’t seem to relate to anything. Modules are a way to call statically from a console application, instead of starting the application through a form, yet are more of a deprecated VB6 feature.
Everything I’ve worked with feels to me as if the VB6 developers just really didn’t want to let go of the language after it became a language of the past with competing languages steadily overtaking. The grammar behind it has been changed into less understandable things based on everything that is taught in the computer science field such as static memory, public, private, and protected access modifiers which are a common grammar amongst many-a-language. Don’t get me wrong, I don’t have a problem with coding in it, and I’m already getting the hang of it, but it just feels as if pushing .NET on VB was a "last hope" of making the language last another 5-10 years.
Sure, it’s all a part of the .NET framework, so the language doesn’t particularly matter all too much, but I honestly don’t see the big hype around it. For a start, it’s nothing new, runtime environments were around for years before .NET came on the scene. The library features just feel like a direct copy of the JDK (another reason why I shouldn’t have much of a problem with getting on with it), and the language itself has just been made to be more understandable, although I believe that’s far from the truth.
Understandability, of course, doesn’t just come from a natural use of language when it comes to software development. As developers, we’re taught to use a standard set of language features, and these are typically copied over into other languages. Compare, for example, C, C++, PHP, Java and more. If you can get on with one of these, then there’s a good chance you’ll feel comfortable with the rest. Some other languages overstep the bounds however, although it does confuse me greatly, because C# fits into a category snugly with Java.
So finally I have to sum it up as follows:
- It’s nothing new
- In effect, it could reduce productivity due to its highly different nature
- It’s all a part of .NET, therefore language doesn’t have much of an impact, this is down to familiarity more than anything
- It’s an old language that has been revived
Again, this doesn’t mean I have a problem with it, and I’m more than happy to work with it, and what I have learnt so far is great as I’m feel more comfortable with it. Perhaps I’ll learn to love it even more so in the future, but I’m honestly shocked at how vastly it is used in the industry today. In fact, a good four or five colleagues of mine are using it in full-time jobs. I guess of course, it’s entirely dependant on the application being developed.

