Re:Why I am called "the Father of Visual Basic" (1996)
by pacaro on Wednesday March 18, 2015 @09:17PM
(#9229710)
I agree with you, but there are some interesting gotcha's in this. Windows 3 accumulated cruft and needed to be cleaned or rebooted regularly. The company I worked for in the late 90's had a public safety customer that ran our code on a Windows 3.0 box, I can't remember the time interval, but periodically one of our developers would go on site and (in NuMega SoftIce - which we habitually ran everywhere) would reset the windows tick counter, and flush crap out of various OS handles tables.
Having done low-level messing about on 16-bit windows, when I moved to Redmond and started working for MS it was hard to drive past BurgerMaster without buying something in homage.
I had simply assumed that VB was Microsoft's attempt to one-up HyperCard, and it's very interesting to learn about VB's real origins.
I developed industrial process controllers using VB. A stripped down Win3 or Win95 system running VB was actually virtually crash proof. Of course this didn't prevent me from incorporating redundancy into the hardware, to take the machine into a safe state if the PC stopped working for any reason.
What the dot net version seemed to do, was to make VB the equal of the other Microsoft languages, feature by feature. The result was that they lost the reason why VB developers loved VB. I continued using version 6 (pre dot net) for several more years after that.