Ruby/VB was a labor of love for us. One of my favorite episodes of Silicon Valley was the TechCrunch Disrupt where every founder said "we want to make the world a better place." It's funny, but true! That is exactly what we wanted to do.
Anyone who likes the "fire an event" story may also enjoy What the Dormouse Said by John Markoff:
I checked your HN profile, and my gosh, if I had even a small part in getting you started in this crazy business, that makes it all worth it.
I feel like my path was so much better because I started from laying out a UI and then learning code as a way to make it do stuff instead of the "lets learn complicated goop with no clear purpose first".
To this day I'm amazed by how ok devs are with not being able to get instant satisfaction from achieving things that should be simple.
They're even adding iOS, Android and web targets. Give it a try!
honestly, i kind if miss vb6's simplicity: you could create a "proof of concept" in the matter of hours, without having to bother with compiling tools, libraries or anything like that. everything just worked.
Did you ever see the sourcecode for it?
How would you tell the VisualBASIC side of this story:
https://www.folklore.org/StoryView.py?story=MacBasic.txt&cha...
I don't think there is a Visual Basic side to the story. Our work was many years after those sorry events.
In fact I never saw the source code for any of the Apple or Microsoft Basics, not even the "Basic" side of Visual Basic. Our team built the "Visual" side of it, code named Ruby. (No relation to the programming language.)
Originally Ruby wasn't going to be combined with Basic at all. It was going to be a user-customizable shell for Windows 3.0. Instead of Program Manager and File Manager, you could create your own desktop with things you wanted on it.
Ruby had a very primitive scripting language, but the language API was designed to allow other interpreters to be plugged into it.
Microsoft later decided to scrap the "shell" idea and create Visual Basic instead.
Did HP coming out with NewWave and its scripting language influence this at all?
And VBX was a pain, but had some advantages over the COM-based controls. My first job at MSFT in 1994 was to build demonstration apps for interactive TV. When I started there was already a base application in VB3. I needed to add transparently layered images and text with rotation and animated transitions, and a windowless VBX made it easy to build that transparency. IIRC, you could not make windowless OCX controls. I'm not even sure how you'd do independently positioned transparent controls in VB4+.
Your kind words mean a lot to me, but more importantly, thank you all for the great things you built using VB.
I'm quoted a few places in it. First, yes, I can assure everyone that the story about the origin of the phrase "fire an event" is true and correct. I could even tell you exactly where I was sitting and which way I was facing when that event fired.
Some things stick in your mind, doobies or not.
Also mentioned is the VBX. In some ways, this may have been the worst API I ever designed. But it was the most successful.
If anyone has any questions, fire a comment!