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

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

One of the most annoying things a developer (who would normally delight in writing code, not futzing with markup) can have is getting rendering issues between different browsers. The two biggest players are of course Internet Exploder and Firefart (as I lovingly like to refer to each). In most cases that's going to take care of 98 percent of your total site traffic. IE has had a proprietary "word-break" style attribute for a long time, and this made it into the CSS 3.0 spec. But that doesn't necessarily help you with Firefox right now. Firefox literally - (and I consider this completely idiotic, since it's been in their bug database for FIVE YEARS) does not have a reliable CSS style element to force table cell content to break in the middle of a word in order to stop the content from expanding your table / div off the page or over other content on the page. Here's a partial fix, which will work for most tables and browsers. The style declaration (I call it m
Read more

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

I've taken a more than cursory interest in the whole Remote Scripting (.NET species) vs. AJAX and now ATLAS discussion, mostly because I started using Remote Scripting since Microsoft first released it, and because I continued to refine it after seeing Brent Ashley's excellent work with JSRS, which was one of the first "real" cross-browser solutions back in 2000 (that's the turn of the Century for you history buffs). Now Bertrand Leroy, a Microsoft guy whose work I like , has authored some very interesting ASP.NET 2.0 script callback stuff that he points to on his blog, and he is obviously (at least, to me he is) involved quite heavily in the development of this new ATLAS infrastructure that they'll preview at PDC. Leroy's most recent post brings to the surface what I agree are the major differences between the "AJAX a - la .NET" approach as popularized by Michael Swartz with his AJAX.NET library, and Leroy's RefreshPanel, the ASP.NET 2.0 b
Read more

IE7 - Vista: "Internet Explorer has stopped Working"

Image
This one was a bitch. All of a sudden for no reason at all, out of the blue, I get this dialog "internet Explorer has stopped working". I didn't install any new software, crap- I didn't do anything! So here I am using FIREFART to go on the internet and find out what to do! Damn! Good thing I've got the sucker on the same machine (I'm not "anti-Firefox", i just don't use it that much except to check my page renderings). The Fix The fix (at least for me): 1) Go into Control Panel, and choose "Internet Options". 2) Under the "Advanced" tab, press the "RESET" button at the lower right: Don't ask me why this happens, or why the fix works. That's a BUG, D00D - I don't care how you slice it!
Read more