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.
Re:Why I am called "the Father of Visual Basic" (1996)
by analog31 on Wednesday March 18, 2015 @09:44PM
(#9229780)
That's a good point, and I may have done inadvertent cruft cleaning just by updating my program periodically, since it was so easy to just reboot the system.
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.