I’ve spent the last few years writing Windows apps in C using the SDK. It’s painful. You have to handle every single WM_PAINT message, manage your own memory, and write hundreds of lines of code just to show a simple dialog box. Then today, I tried the new Visual Basic 1.0 from Microsoft. My jaw is on the floor.
From Coding to Drawing
In VB, you don’t write code to create a button. You select the "Button" tool from a palette and draw it on a form. You change its properties-like its Caption or Name-in a sidebar. It’s "Rapid Application Development" (RAD) in its purest form.
But the real magic is the "Event-Driven" model. You don't write one giant message loop. You double-click the button and write code for its Click event.
' This is all it takes to make a button work in VB 1.0
Sub Command1_Click ()
MsgBox "Hello, World!"
End Sub
The language itself is a modernized version of QuickBasic, which many of us already know. It’s simple, it’s readable, and it hides all the ugly Windows API calls behind a friendly facade.
The Extensibility: VBXs
Microsoft also introduced "VBXs"-Visual Basic Extensions. If the built-in tools aren't enough, third-party developers can create new controls that you can just drop into your project. I’ve already seen charts, grids, and even database connectors. This is going to create a whole new ecosystem of "component" software.
Looking Ahead
Professional "C" purists are already scoffing at VB, calling it a "toy." They’re wrong. While it might not be the right tool for writing a device driver or a high-performance game engine, it’s perfect for the 90% of business applications that just need to get data from a user and put it in a database. Visual Basic is going to democratize Windows development, and I suspect we’re about to see an explosion of custom software like never before.