1. If you've ever heard of TurboVision, this UI is similar to it. But actual TurboVision as it was later to be found in Borland programs, and as even can be found in clones today, did not have this look and feel, which would have seemed a little clunky for a TUI by the end of the 1980s.
1. Notice that F1 is already help, but the other function keys do not follow the CUA pattern that was only actually formalized that same year.
1. Notice the differently coloured letters for the shortcut keys for menu entries, something that has largely vanished nowadays.
1. Notice how wasteful of 80×25 area some of the windows are. It was not long before everyone had shrunk the application menu down to 1 row. Conversely, though, look how colour is used to demarcate function key names, rather than using square brackets.
1. Scroll Lock is actually a major part of the user interface. A number of MC/PC/DR-DOS programs at the time gave a use to Scroll Lock. In Turbo BASIC, it switched (as it says in the screen shot) into and out of a mode where the arrow keys moved/resized things.
This interface is magical when comparing with Turbo Pascal 3.3 and 4.0.
I don't recall any longer correctly, but I think Turbo Basic even supported dual monitor debugging sessions.
Miss those days. When I got a 386 and could use the turbo debugger to hack games. Pretty sweet. Just run the code; interrupt it near where it was asking for a word or number or clicking a symbol, then tweak a flag and let the game continue.
So often the final fix was to nop out an instruction that set a flag and just let it fall through.
Then there was the DSI team in Vancouver who encrypted their boot code...
Had Borland not been so expensive or had the stranger on IRC known or told me GCC existed for DOS/Windows who knows where my career would be today.
In a weird way though I never used it, hearing about Borland Turbo anything still makes me happy because it reminds me of something I thought was unobtainium.
I feel this. I recall distinctly back in the mid '80s my mom, talking about my intense interest in computers: "It's great to have a hobby, but at some point you're going to need to figure out what you want to do for a real job."
And here I've turned my hobby into a living.
Tandy CoCo 2. Followed by a 386 20Mhz where I graduated from Basic to Turbo Pascal and Turbo C++
Well, I got the last laugh on that one.
DJGPP rhide and allegro that was my gateway drug!
I still miss Turbo Pascal (and later Delphi) ... not so much the language, but the speed of feedback was unparalleled.
But this was a great boon to me because it gave me a highly spec'd 486DX in the early 90s.
The side-by-side 'dir' command demo he did was pretty impressive.
Somebody down the chain got his 386 and somebody else got their 286.
I sometimes look at my pre-2024 workflows and feel like I'm looking at a caveman's toolchain. Absolutely bonkers as to how quickly we humans adapt to things.
Also, neat bit of trivia: Borland was originally named MIT ("Market In Time"). The OG MIT in Cambridge, MA, sent a trademark letter and they then changed their name to Borland, which was supposedly a client of theirs.
It’s complicated. Especially because we had a huge regression in programming from roughly the mid-90s until recently.
In the early 90s I used Turbo Pascal as a kid. It was an editor with an awesome built-in debugger, profiler, online help, super fast compiler. This all culminated into Delphi, which had all that and offered drag-and-drop UI building.
Programming regressed a lot after the demise of Borland IDEs. Especially on Linux/Unix the tooling was very primitive in comparison.
In a very weird way, LLMs brought back a bit of these old environments in the sense that you can use one interface for programming, debugging and profiling. It just does more of the boring work for us (cross-referencing code, writing profiling cases, etc.
Other than that, LLMs, etc. would be so foreign for someone from the 80s that their minds would be blown and it would look like alien technology.
Thus I don't have the same affinity to QBasic, as others do, I had already enjoyed compiled BASIC and systems programming in BASIC by the time MS-DOS 5 came out.
Great memories, and eventually made the jump into Turbo Pascal.
https://github.com/skx/cpmulator
There's also a repository of curated/vintage programs, including Turbo Pascal here:
https://github.com/skx/cpm-dist
I still tinker with it, now and again. Though I admit I get distracted and mostly run stuff under BBC BASIC (with it's integrated assembly support), and then switch to replaying Zork!
https://archive.org/details/000376-BorlandTurboBasic10>
https://archive.org/details/BorlandTurboBasic1.0German
https://archive.org/details/turbotoolbox
In the time I was willing to spend, I did not see a 1.1 release.
1. You can see them in my recent submissions. Don't want to shill.
VS Code had a little bit of that feel, but it's grown so much and added so many features that it's lost it. And the closest thing I've found to the feeling of writing C in the 90s was Arduino sketches a decade ago.
But oh, the license. "Use it like a book". That is, any number of people can use it, but only one at a time. And it was like two paragraphs, and written for humans, not lawyers. Amazing.
Turbo Pascal was just genius, really!
Esp. the lightspeed compile times, and that you could create a redist exe-file to copy your "highly sophisticated games" to your friends and show them, how cool it is :-))
Good ol times!
QB64 is pretty popular as a sort of QBASIC-dialect with additional features like OpenGL, multimedia support, etc.
FreeBasic is decent as well but its focus is more on being a compiler whereas QB64 aims to be more batteries-included with its builtin IDE.
* https://news.ycombinator.com/item?id=49942103
Whilst the 'Phoenix Edition' above states that the old QB64 pages are off-line, in fact there do still seem to be some around today. I don't know what the history is here. Whatever it is, it seems to have been fixed.
* https://github.com/DualBrain/QB64
QB64 in turn points to PC-BASIC, a clone of the old GW-BASIC with at a quick glance nothing really modern going on:
I eventually replaced dBase with Turbo Pascal plus a library named Topaz that offered most of the relevant functionality (including reading/writing DBF files).