Dim a : VB Is Not a TypeOf Misanthropy

After copping a bit of a bollocking at the hands of the masses the other day, Paul Vick has thrown out some reasonably insightful diatribe regarding proposed code re-writing functionality which is slated for inclusion in an already feature rich IDE.


In it he mentions the overwhelming number of responses received from the community for his recent "Refactoring" entry; I don't think that it's really that remarkable. As the world of blogging surges towards saturation point, words from those in positions of influence will increasingly be turned to (and turned upon) for low-level scrutiny. The chaos and commentary which ensued is an inevitable reaction that will occur when language designers talk about languages, or salespeople talk about sales, or motivators talk about motivation, or lazy Australians talk about.... ahhh nevermind! The thing is, the level of interest proved that people found it interesting and I'm sure that it made everyone question their "belief" in that understanding and position towards that topic.

I think that, if I were in a position to influence the focus of the VB Team I say this: forget that code re-writing stuff, let the C# guys sweat the details of that. Let's continue to focus on the next wave, but, as an aside, keep selling ways to use the language to build useful applications - that's where the real added value in VB is *and* was.

One thing that Paul said that I took note of was:

That’s because they don’t necessarily have the time or the extra available energy to spend exploring the nuances of Visual Studio, not because they are too stupid to figure it out...

Keep swingin' Paul - we're still miles ahead in designer experience! ;-)


  • VB.NET developers will now not made familiar with the term Refactoring which is a general term used by Java developers, C++ developers, researchers, architects and soon, C# developers. VB.NET developers will never hear of the term and will not learn about the term. They will thus not be able to participate in discussions about this and will be looked upon as second grade developers.

    Sorry, but EXPLICITLY avoiding a menu item with the general term is EXPLICITLY making VB.NET developers look less skilled while they probably ain't.

  • > VB.NET developers will now not made familiar with the term Refactoring

    Well, they already are but that's an aside. I've used this feature, it's not really that great. IMHO it should really be relegated to more speculative ventures - such as WebMatrix - until it has been further evaluated.

    Frans, on another (completely unrelated) topic, are you a C# developer? If you are can you please tell me how often the average C#'er would use the C# Class wizard when designing classes and their respective members? Is that a useful IDE tool?

  • Well, it's speculation of course if the average VB.NET developer is familiar with the 'refactoring' term, however he/she will be when there is a menu item in front of his/her nose :)

    Refactoring is not something I'd use often agreed, as I'm more of a design first, implement later kinda guy and not a 'design on the fly' kind of developer, however refactoring can help.

    I'm a C# developer and I never use the class wizard. :) I also don't know any C# developer who uses the wizard to, say, add properties. Most of them have macros for that. The class wizard is pretty bogus to me, because it f.e. doesn't do a lot you would expect from such a wizard, like creating a derived class from a given other class, implementing interfaces using the wizard etc.

  • Right, thanks. Well, I'd estimate that the 'Refactoring' stuff will get used nearly as much as the C# Class wizard does :)

Comments have been disabled for this content.