Reply 20 of 89, by Jo22
- Rank
- l33t++
jakethompson1 wrote on 2023-09-07, 00:39:davidrg wrote on 2023-09-06, 22:57:I believe a lot of telescope control stuff for Windows (eg, EQMOD) is built with Visual Basic 6 just because there are a bunch […]
Peter Swinkels wrote on 2023-09-06, 09:21:So in short, does anyone here still use these for a hobby or even practical reasons?
I believe a lot of telescope control stuff for Windows (eg, EQMOD) is built with Visual Basic 6 just because there are a bunch of standards based on COM and its easier to build COM stuff in VB than in C++
But today unless you're targeting vintage DOS/windows I don't know there is any practical reason to build new stuff in these old languages.
Today Python is a better "beginner" language than BASIC while also being a serious language suitable for building real software in.I believe VB6 technically lives on within VBA
Yes. And VB6 has another advantage, its applications run from Windows 98 to Windows 11 without any doing.
The core libary, msvbvm60.dll, is still included since the Windows 98 days and has a "just works" type of status.
I vagueley remember there are also a few VB6 compatible languages that use Java etc, but they're not as popular.
What differenciates old VB Classic from "modern" languages is that it was a fine RAD IDE (Rapid Application Development IDE).
It was very useful for prototyping, for writing a sample application or a dummy (functionless input mask) of what should latter become the real application.
However, and that's the irony, many sample/demonstration programs ended up being good enough so that they were actually being used.
And that's a circumstance what I think is barely understood/remembered.
VB Classic was used by a lot of layman, which weren't Top Gun type of programmers (those C++ elitists).
They rather were experts in their own field, rather than programming.
However, because they knew their fellows, they could program applications in a way that suited them.
So the final application perhaps wasn't great from a code point of view, but the look&feel and the functionality was.
That's why that bus driver vs fight jet pilot comparison comes up sometimes.
Some of the VB Classic programmers were just happy to be bus drivers.
And that's why .NET killed off VB as a language, the simplicity of original Basic was gone.
That's also why Delphi was so popular for a while, it was same principle, but based on Turbo Pascal/Object Pascal.
Edit: The 16-Bit line of Visual Basic (1.0 - 4.0 16-Bit) supported VBX modules (control sets), while VB5/6 used .OCX..
That's also a reason why VB3 was popular for so long, even in the Windows 95 days. It was close to VB4, but faster&slimmer.
There used to be a market for VBX modules in the 90s (the shareware scene alone was full of it).
A VBX was like a special DLL that could be easily imported in an VBX compatible application, like a plug-in.
Just think of a VBX that comes with a database, a piece of hardware (interface etc), a game.
If a VBX was loaded, it often visually appeared in the IDE as a new set of Windows standard controls.
Delphi 1.0 also supported VBX controls, I vaguely remember.
Edit: Also interesting: VB Classic was compiling applications to use P-Code by default.
It's some sort of pseudo code, with a virtual machine executing it. It's not really interpreted code, though.
Rather, it's similar to CHIP-8 or Java. And that's not bad per se, maybe. It can be near as efficient as native x86 code, depending on situation.
However, VB6 Professional and higher support compiling to i386 machine code, as well.
In the business world, this feature was rather used for another purpose, though. To make disassembly more difficult.
"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel
//My video channel//