Monday, January 20, 2014

RE: VB.NET and C#

A friend of mine sent a link to a article listing down ten reasons on why VB.NET is better than C#. I attached that link in this post.

Whatever the author described about VB and C# is true,  but the conclusion is subjective.

Looking at the something or when you are facing the same description, you would get different conclusion when you look at it from different angle…

Thing as simple as “case sensitivity”  is not different, different angle will get different conclusion…

for a guys like me, was a VB6 expert and moved on to C#. I can appreciate both angles… what I want to say is  from VB to C#, it is a paradigm shift. Once you completed that shift you will be able to see both side.

It is true to C#  ( Java , or C++) programmer also. if the guy never try to understand the other side the fence. he or she would never understand why VB programmers think the way they do…

In VB.NET, If you define a property without specifying  type, it is fine;  if you have a function without return statement, it is fine; if you have function without return type, it is fine….

These in C# is unimaginable. you could say VB is more flexible ( relax)  than C#, you could also say C# is more rigid ( adjective) than VB. it is all depends on your prospect when you look at it.

VB.Net as it is now , good or bad, is due to the legacy it carried from VB. However, language is just a language, it is used to describe our thoughts only. it is our thought that matters.
  




No comments:

Post a Comment