Skip to main content

R.I.P Visual Basic

Are Visual Basic days numbered?

Over last few weeks I have been hearing that Microsoft is going to stop supporting Visual Basic at some point in future. C# is the language of future. Here, according to some, are few evidences of it.

1. There are new versions of C# but no major development in VB.net
2. Microsoft uses C# for example in most of the articles/journals.

Do a quick search on "VB.Net a dead language" and you will find some interesting article.

I would like to hear your views on this. Personally I think C# is a much better language than VB.Net even though most of my experience has been in VB. The syntax of C# is much more clear and easy to understand. I must say I am converted and given a choice I will prefer coding in C#.

DebugGuru

Comments

Post a Comment

Popular posts from this blog

Why there is semicolon at the start of a JavaScript function?

Very often while reviewing the code for my team, I will come across a semicolon at the start of JavaScript function as show below ; (function () { 'use strict'; ...and I often wondered what purpose it served. Guess what. It is an insurance to make sure your script works fine when all other scripts are merged together;  The leading ; in front of immediately-invoked function expressions (iffe) is there to prevent errors when appending the file during concatenation to a file containing an expression not properly terminated with a ;. So there you go. Now you know what that little semicolon is doing there in your code.
3 comments
Read more

C# Performance Improvement - The Power of StringBuilder

 Often when we are wring code we don't think about performance and go with the default options available to achieve a task. String concatenation is one such scenario. If you are doing simple and few string catenations, then you can use the following result = string1 + string2; string1+= string2; result = String.Concat(string1,string2); String.Format and string interpolation are few other options.  However when you are performing large and repetitive  operation, string catenation can be expensive. Here is an example to prove the point.  As you can see it took 41 seconds to perform 100k string catenation. Now lets replace this with StringBuilder and see.  8 ms!!!!!! That is a massive performance difference. Hope you get the point. More info on StringBuilder can be found here https://learn.microsoft.com/en-us/dotnet/api/system.text.stringbuilder?view=net-7.0
Post a Comment
Read more