On Sustainable Software Development
Wednesday, March 30th, 2005I’ve been reading quite a few articles the last days on how Microsoft is dropping Visual Basic 6 in favor for versions built on the .NET framework. This has angered quite a few businesses that market software for the Windows platform that are written in VB6 since the newer versions of the compiler are incompatible with their sourcecode (or vice versa). Not only do they lose their development platform, Microsoft isn’t putting support for the VB6 runtimes on their upcoming operating systems at a high priority. This leaves all the VB6 developers with a rotting codebase and with rotting operating system support.. and the decision to either rewrite their products or dropping them from the pricelist. Gee, now thats a healthy development environemnt if I’ve ever seen one. Microsoft is marketing the VB.NET as the alternative for these developers but the big question is, for how long and when will that compiler be replaced aswell?
There is an important lesson to be learned from this, by using compilers and/or languages based on closed standards and implementations you jeopardise your your product and hand over your business decisions to the compiler vendor. Why? If all these millions of products that now face an uncertain future had been written in an open independent language such as C, C++, Perl, Lisp, Java or insert favourite language here this would never be a problem.. and not only that, the customerbase would be even larger since the product wouldnt be locked in the Windows family of operating systems. Only support the customers running Microsoft products is like a car vendor only supporting users driving on tarmac.. Most of these developers will however choose to wander along on the Microsoft path and go ahead with .NET arguing that Microsoft actually promised support for it until 2012.. and then back to square one.. and they will give you the old “that software will have been replaced by then” argument.. remember Y2k?
The Visual Basic community is standing at a crossroad that all Microsoft users/developers/resellers/etc either already have faced or will face (again and again and again). They can either choose to go ahead and continue to lock themself in, letting their business decisions be steered by Redmond (and their wallets drained in the same direction) or they can look around them and find a world full of alternatives that give them full unconditional freedom. Just like Instinct Soft once proclaimed now in an updated slogan-version, Open Source, We kick your ass for free!.