I was a pretty successful BASIC programmer, starting on DEC PDP-11 RSTS/E BASIC. Line number BASIC was good enough for simple applications, but quickly turned into spaghetti code.
Later, the VAX had BASIC with functions and subroutines and dropped the line numbers and this version of BASIC was significantly better. It was procedural, but you could organize your code into modules, keeping it readable and maintainable.
Eventually the non line number BASIC spread to the PC. Microsoft Professional Development System, then Visual BASIC.
I was writing BASIC code for everything until a few years ago -- VB.NET -- until it was really clear that it had become a totally second-class citizen and I switched to C#.
I still think VB.NET is vastly more readable than C/C#/Java etc.
I never ended up trying VB.NET, but I spent a lot of time in middle school playing with VB3 and later VB6. Being able to drag and drop components to quickly scaffold out a WYSIWYG GUI which you could then double-click on to create premade handlers was the veritable cat's meow.
I feel like that kind of event-driven programming model was very intuitive, even for younger audiences.
All of that stuff is still in the latest Visual Studio 2026. VS2026 looks basically identical to VB6. It's still great if you're making little desktop apps by hand and you can back them with any .NET language, e.g. C# etc.
Some people love to complain in the whole VB vs VB.NET, because VB.NET dropped several VB 6 stuff on .NET 1.0, however .NET 2.0 re-introduced some stuff back, but they were no longer paying attention.
And designed to be compiled from the start, the interpreters in 8 bit home computers were due to hardware limitations, after the 16 bit transition compilers were back in.
You really felt productive doing anything with Visual Basic 6, at least until things slowed to a crawl because it wasn't so performant or it was held back by the typical Access database. You didn't need 200 hours of YouTube tutorials about the front-ed UI framework du jour to get going.
VB.NET and C# was treated as equals for a long time. I believe MS initially expected VB.NET to be the mainstream .net language, while C# was a compromise to attract Java and Delphi users.
But the transition from VB to VB.NET was not handled well. VB was very well liked by its users (even if non-users looked down on it) but VB.NET was worst of both worlds. Too different from VB to be smooth upgrade, and still nok considered as professional a language as C#
C# has gained tons of features and improvements of existing ones, VB.NET has unfortunately been fully ignored. Not even put in the back burner, just left to die, apparently. Which is sad, because I find it more legible and beginner-friendly than any C-derived languages.
I truly and genuinely do not understand why you'd do something like this not open source? You definitely lose popularity and participation, and today, you almost definitely also lose money.
> why you'd do something like this not open source
The project started in 2003 - the market was different then. Curated products of that kind were normal (and an honest linear attempt to finance the endavour).
too bad it's for win, raspberry pi, arduino, esp32, etc need this sort of stuff. lot's of hardware folks who just want to do hardware and not learn programming. they might eventually learn python or C, but BASIC would be so much better.
A Raspberry Pi/ARM port is the most realistic next step; microcontrollers are a different beast. For ESP32/RP2040 today, MMBasic/PicoMite is worth a look.
The interesting thing would be if someone made a lookalike for Visual BASIC for DOS (not Windows) that ran as a standalone EFI application.
That is the real 'what if it had not gone out of fashion' path. VB/DOS definitely went out of fashion. GUI BASICs became fashionable, instead. Everyone who does a 'visual' BASIC nowadays does a GUI one.
The headlined BASIC is nothing like a VB/DOS for EFI, though.
Oh yes. They were definitely graphical. No two ways about that.
I'm talking more about the distinction between VB/DOS and VB/Windows. They both did the whole WIMP thing, with a visual editor to construct the forms for one's programs, but VB/DOS used a TUI rendering that drew everything with VGA character graphics and used the firmware low-level keyboard access for input; whereas of course VB/Windows used the Windows GUI.
A VB/DOS-alike that ran on EFI and did the whole form-based programming thing, would use the EFI text input and output protocols, which know Unicode, waiting for events, and standardized scan codes and modifiers.
There is no major call for it, as you say, when bootstrapping an entire operating system is so easy. But it would be interesting to see someone tackle it from the point of view of what VB/DOS would look like today if it ran directly on the firmware, spoke Unicode, and ran in protected mode
Nice to see another VB/DOS aficionado! One of my first summer jobs that didn’t involve landscaping as a teenager was porting a CAD-based application from VB/DOS to Visual Basic 6 so it could run natively on Win9x machines.
It tells a specific counterfactual story, but it's one that has a reasonable background for it.
If you were a new computer user in 1980, your Appie II+ or PET 8032 booted straight into BASIC, and it was a good-enough tool that could do productive development for the entire life of the machine there.
But if you were a new computer user in 1990, you didn't have that. They gave you GW-BASIC, and if you're lucky a separate manual rather than a vague chapter in the main DOS manual. This might be enough to give you some initial experience with programming, but you have a bunch of hard brick walls.
Your machine might have 640k-4Mb of memory, but GW-BASIC can only meaningfully work with 64k of it.
You can't access the mouse or any post-EGA graphics modes without a LOT of assembly shimming. If you had a sound card, it was outside the built-in tooling.
Remember, this is a few years before the Internet being widely available, and stuff like the GNU project being widely accessible. This is probably the best development tool you have available
If you wanted to go further in programming, it meant buying a boxed compiler that probably cost well in excess of USD100, and was for a completely different language than the one you had cut your teeth on.
But if you wanted "The GW-BASIC I already understand, but more", you want this.
It was not the future of the language. It's starting, as the blurb says, from where GW-BASIC and the old Microsoft BASIC were in the early 1980s. We know what the actual future of BASIC was after those, because that future happened. It wasn't this at all.
Structured BASIC dialects have function-local variables, BASIC dialects that support linking separately compiled modules support exported and non-exported variables, etc.
Later, the VAX had BASIC with functions and subroutines and dropped the line numbers and this version of BASIC was significantly better. It was procedural, but you could organize your code into modules, keeping it readable and maintainable.
Eventually the non line number BASIC spread to the PC. Microsoft Professional Development System, then Visual BASIC.
I still think VB.NET is vastly more readable than C/C#/Java etc.
https://www.remobjects.com/elements/mercury/
The real Visual Basic not by Microsoft is TwinBASIC(closed source).
I feel like that kind of event-driven programming model was very intuitive, even for younger audiences.
https://www.codemag.com/article/0505051/What%27s-New-in-Visu...
Unfortunately it was a one-to-one match to C#.
It would have been much netter if it was based on Visual Basic 6
VB.NET and C# was treated as equals for a long time. I believe MS initially expected VB.NET to be the mainstream .net language, while C# was a compromise to attract Java and Delphi users.
But the transition from VB to VB.NET was not handled well. VB was very well liked by its users (even if non-users looked down on it) but VB.NET was worst of both worlds. Too different from VB to be smooth upgrade, and still nok considered as professional a language as C#
VB.NET can do everything what you can do with C#. Saying that C# is better than VB.NET is like saying that French is better than Spanish.
For example, the new async/await runtime model is also for VB.
VB 6 way to do COM still wins out, though.
Show HN: I wrote a BASIC interpreter that boots on UEFI machines - https://news.ycombinator.com/item?id=49410814 - Aug 2026 (44 comments)
Check PureBasic. https://www.purebasic.com/
Compiles to native, interfaces to C libraries, available on most platforms...
Fast during development, fast results, flexible, well conceived, a pleasure to work with...
The project started in 2003 - the market was different then. Curated products of that kind were normal (and an honest linear attempt to finance the endavour).
That is the real 'what if it had not gone out of fashion' path. VB/DOS definitely went out of fashion. GUI BASICs became fashionable, instead. Everyone who does a 'visual' BASIC nowadays does a GUI one.
The headlined BASIC is nothing like a VB/DOS for EFI, though.
That wasn't the case with GW-BASIC, due to how MS-DOS came to be.
However the idea of an EFI BASIC does sound rather nice, assuming the whole plethora of graphics programming as well.
Other take the easy way out with RISC OS for the Raspberry PI, which has BASIC as main programming language alongside Assembly.
I'm talking more about the distinction between VB/DOS and VB/Windows. They both did the whole WIMP thing, with a visual editor to construct the forms for one's programs, but VB/DOS used a TUI rendering that drew everything with VGA character graphics and used the firmware low-level keyboard access for input; whereas of course VB/Windows used the Windows GUI.
A VB/DOS-alike that ran on EFI and did the whole form-based programming thing, would use the EFI text input and output protocols, which know Unicode, waiting for events, and standardized scan codes and modifiers.
There is no major call for it, as you say, when bootstrapping an entire operating system is so easy. But it would be interesting to see someone tackle it from the point of view of what VB/DOS would look like today if it ran directly on the firmware, spoke Unicode, and ran in protected mode
A Phoenix like BIOS UI.
If you were a new computer user in 1980, your Appie II+ or PET 8032 booted straight into BASIC, and it was a good-enough tool that could do productive development for the entire life of the machine there.
But if you were a new computer user in 1990, you didn't have that. They gave you GW-BASIC, and if you're lucky a separate manual rather than a vague chapter in the main DOS manual. This might be enough to give you some initial experience with programming, but you have a bunch of hard brick walls.
Your machine might have 640k-4Mb of memory, but GW-BASIC can only meaningfully work with 64k of it. You can't access the mouse or any post-EGA graphics modes without a LOT of assembly shimming. If you had a sound card, it was outside the built-in tooling.
Remember, this is a few years before the Internet being widely available, and stuff like the GNU project being widely accessible. This is probably the best development tool you have available
If you wanted to go further in programming, it meant buying a boxed compiler that probably cost well in excess of USD100, and was for a completely different language than the one you had cut your teeth on.
But if you wanted "The GW-BASIC I already understand, but more", you want this.