We Don't need no Steenking Vee Bee Dot Net!

This Richard Grimes thing has really fired up a lot of people! The guy is a pro, he can say whatever the hell he wants in his parting shot at DDJ. So he put down .NET and made a bunch of predictions.Who cares! When .NET first came out I clearly remember one JAVA guru calling it "Vaporware".

You really don't want to engage too much in mental masturbation over this kind of thing. Maybe he was having a Senior Moment. Maybe somebody in Redmond got him pissed off. One thing I know,
his comments about VB.NET were right on. We don't need no steenking Vee Bee Dot Net! Nyaaa, Nyaa Nyaaa!

It's not the language itself (although I've come to hate it). What it really is: Microsoft tried to create a new language for marketing purposes, because of all the billions ( a la Carl Sagan) of VB develpers out there. In doing so, they perpetuated all the helper classes and crutches and Option Strict=off and Option Explicit = off and the result is you have beelions of crybaby VB developers now doing .NET and they are being allowed -- even encouraged --to write crappy code and get away with it. The VB.NET compiler compiles it - it doesn't even whimper. I am humiliated almost daily by the C# compiler - I have to write quality, strongly typed code. And all this stuff about case insensitivity is a buncha baloney! What, they are gonna redo the UNIX filesystem because you think case insensitivity is passé?

If you want to feed a man for a lifetime don't give him a VB.NET fish. Let him learn C#. Look at the Enterprise Library. All C#. Look at ASP.NET - all 1 million plus lines of code -- C Sharp. What are we talking here, Greek?

Hanselman got it right when he said: Set VB6=Nothing.

I say, Set VB.NET = VB.NOT!

Comments

  1. Anonymous6:15 PM

    http://blogs.msdn.com/danielfe/archive/2005/02/22/378343.aspx

    I think Dan Fernandez handled this well. In some ways, made Richard look like a chump. Heck of a way to go.

    ReplyDelete
  2. Anonymous2:13 AM

    You're right. Writing System.Console.Write("Hello World"); instead of System.Console.Write("Hello World") is so different. You have to understand that it's possible to write good code in VB.NET as well as in C#, it doesn't depend on the language or the background, but on the developer's talent.

    ReplyDelete
  3. Anonymous4:02 PM

    IMHO, the basic problem with VB.NET is that it makes it too easy for bad programmers to write poor quality code. This is a huge disadvantage but not one that cannot be overcome (mostly) with the right settings and some programmer discipline. The first thing I do whenever I start a new VB.NET app is to turn Option Strict On and remove the reference to the Microsoft.VisualBasic.* namespaces. This will eliminate 75% of the problems.

    The better VB.NET programmers know to turn on Option Strict

    ReplyDelete
  4. Anonymous9:58 PM

    We may not need Vee Bee Dot Net but where would we be without veebees.com I ask you???

    ReplyDelete

Post a Comment

Popular posts from this blog

Some observations on Script Callbacks, "AJAX", "ATLAS" "AHAB" and where it's all going.

IE7 - Vista: "Internet Explorer has stopped Working"

FIREFOX / IE Word-Wrap, Word-Break, TABLES FIX

System.Web.Caching.Cache, HttpRuntime.Cache, and IIS Recycles

FIX: Requested Registry Access is not allowed (Visual Studio 2008)