I don’t agree with Steve that Visual Basic 6.0 should go. The world is full of developers with a wide range of skills and talents. Many are (what I call) “paradevelopers”—those with other interests or professions that simply want to write a simple Windows program. These doctors, lawyers, receptionists, students, moms and dads have a tough enough time as it is with the fundamentals of programming. To force them to use OO programming disciplines is arrogant.
I expect that many of the issues you’re seeing in the healthcare industry (where I worked while at EDS) have to do with the data store many hospitals and providers are using—JET. No amount of OO discipline will help protect a JET database from being compromised or damaged by inept users.
Nope, Visual Basic 6.0 might not be right for Steve’s shop and I think that disciplined programming is a good idea. I just don’t want to kill the language because it does not seem to meet the needs of an OO purist. There are plenty of serious developers using disciplined coding techniques creating safe applications with Visual Basic 6.0.
I expect that many of the issues you’re seeing in the healthcare industry (where I worked while at EDS) have to do with the data store many hospitals and providers are using—JET. No amount of OO discipline will help protect a JET database from being compromised or damaged by inept users.
Nope, Visual Basic 6.0 might not be right for Steve’s shop and I think that disciplined programming is a good idea. I just don’t want to kill the language because it does not seem to meet the needs of an OO purist. There are plenty of serious developers using disciplined coding techniques creating safe applications with Visual Basic 6.0.
Leave a comment