18 March 2005
Transitioning to... VB6?!
As so many others have posted, there is a petition going around to “save” VB6.
The real irony for me is that within what must has been hours of first hearing this, I was on a conference call where I learned of a project to update an application from 16-bit VB (2, I think) to VB 6.
The reasoning was that it might be too hard to port this app to .Net. As though porting anything 16 bit to a modern language would be easy. They had to find a Win95 machine to just install the program for creating the project spec document! More than likely, the other developers on the call hadn't really looked at VB.Net yet, at least not enough to know that almost everything they knew about VB6 syntax would still be applicable. I know some of them at least had done some C# training, and of course there are those who forget that .Net supports VB too. Not to mention the fact that a program newly written in VB6 and COM will forever live in a silo, because none of the .Net programmers on my team will ever be leveraging the code for this major production system.
As a VB.Net programmer, I find this story just plain sad on so many levels.
Comments