3 ms·
I worked in a start-up straight out of college where I had done C/C++. We decided to try out this Visual Basic to see if we could get things done more quickly.
by discreteevent 10y ago
I worked in a start-up straight out of college where I had done C/C++. We decided to try out this Visual Basic to see if we could get things done more quickly. VB 3.0. I was blown away by how quickly you could do things even though the language made it hard to organise any kind of structure when things got bigger. We did a lot of work in it and I assumed something like it was the future of programming.
Then the start up went bust and I was back to C++ before any newer version of VB came out. They really got reusable components right. I've never had an experience since where there is such a huge jump in productivity with a new technology.
- fiddlerwoaroof 10y agoI started with similar tools: Borland Delphi and the Object Pascal language.
- fiddlerwoaroof 10y agoI'm not really sure of the timeline, but I think Delphi pioneered the "reusable components" paradigm and VB was Microsoft's entry into the market.
- ryanhuff 10y agoDelphi came after VB3. VB3 had "custom controls" called VBX (Visual Basic Extensions), which were the reusable components. It was the precursor to OCX and ActiveX controls.
- probablybroken 10y agoYes - I migrated from VB -> Delphi - one of the big advantages at the time was you could compile a small executable that didn't require you to distribute several additional disks of vb runtime DLLs with your software.