4 ms·
I distinctly remember being taught BASIC in school in the 1980s and quickly thinking “this is awfully basic” and not wanting much to do with it. Now I don’t kn
by duxup 3y ago
I distinctly remember being taught BASIC in school in the 1980s and quickly thinking “this is awfully basic” and not wanting much to do with it.
Now I don’t know if my childhood evaluation was correct but I do wonder:
Were there many complex programs written in BASIC? Or was it largely a teaching tool?
- pjmlp 3y agoPlenty, outside 8 bit computing, BASIC was structured and had enough compilers to chose from.
- ajross 3y agoLots and lots of BASIC was used in production for routine IT-ish tasks at the dawn of the personal computing era. It was the only meaningful way to implement custom tasks until the mid-80's when environments like Turbo Pascal showed up. For years and years technically-savvy small businesses were buying Apples and PC's and then writing their own BASIC to glue together whatever automation they needed. Was much commercial software written in BASIC? (Edit, because this is being misunderstood: I'm not talking about the evolved BASICs being pushed by the late 80's, only about the ones like Applesoft and GWBASIC the commenter is asking about) No, very little. As you point out BASIC doesn't offer much to developers who already understand a macro assembler. But the market was much bigger than that.
- SoftTalker 3y agoThere was some business use. https://en.wikipedia.org/wiki/Business_Basic https://en.wikipedia.org/wiki/Business_Basic Was popular with some smaller companies for their internal custom systems. Had some similar capabilities as COBOL without the IBM tax.
- skissane 3y ago> Had some similar capabilities as COBOL without the IBM tax. COBOL never had an "IBM tax", because almost every non-IBM vendor had a COBOL compiler. If you didn't want your COBOL from IBM, you could buy it from DEC, HP, Wang, Unisys, NCR, Honeywell, Microsoft, Micro Focus, Watcom... That said, if your COBOL was running on an IBM platform, you often were using lots of IBM proprietary features (e.g. CICS) which made it hard to port to another vendor–and that could indeed be an "IBM tax". But that's wasn't due to COBOL in itself. If you limited yourself to standard COBOL, and avoided IBM proprietary stuff, moving your COBOL app to another vendor didn't have to be difficult BASIC attracted business users because it was viewed as simpler and easier to learn, because it could run on smaller machines, because (often) using an interpreter instead of compiler resulted in faster development (no edit-compile cycle).
- chasil 3y agoA free copy of DEC's original COBOL compiler for the VAX can be found in the VMS 1.0 image at this site: https://www.wherry.com/gadgets/retrocomputing/vax-simh.html https://www.wherry.com/gadgets/retrocomputing/vax-simh.html Modern GNU COBOL can be found at this site: https://www.gnu.org/software/gnucobol/ https://www.gnu.org/software/gnucobol/ A great deal of the COBOL that we use relies on OS2200 DMS, originally from Univac.
- skissane 3y ago> A free copy of DEC's original COBOL compiler for the VAX can be found in the VMS 1.0 image at this site: Where? I don't see any VMS 1.0 image linked to on that page. Instead I see instructions to join the HP OpenVMS hobbyist program, which no longer exists, in order to install OpenVMS 7.3 on an emulated MicroVAX. There is no longer any hobbyist program offering legal access to VMS for VAX. HP's hobbyist program was terminated and replaced by VSI's, which never included VAX (and more recently they appear to have dropped Alpha and Itanium, making it x86 only). Licenses to legally run VMS for VAX are very limited (e.g. maybe buy a used MicroVAX or VAXstation which comes with a VMS license)
- chasil 3y agoSorry, I posted the wrong link. I have downloaded all of this and run it on a rhel9 clone. https://gunkies.org/wiki/Installing_VMS_V1.0_on_SIMH https://gunkies.org/wiki/Installing_VMS_V1.0_on_SIMH
- skissane 3y ago> Was much commercial software written in BASIC? No, very little. There was a huge amount of commercial software written in BASIC dialects such as classic Visual Basic and ASP, Pick/BASIC, HP Business Basic, Wang 2200 Basic, DEC BASIC-PLUS, etc. Boring business software you would likely have never heard of but which was (and in some cases still is) essential to running all kinds of different businesses. I used to work for a university and both the student administration system and the accounting system were off-the-shelf software, mostly written in VB6 and classic ASP (I believe the vendor also had some COM components written in C++, they had their own app framework, but the business logic was all VB6). At the time, we were waiting for the vendor to finish porting it to VB.NET. 20 years later, it probably still is in VB.NET.
- Locutus_ 3y agoI was surprised to get an email today notifying me of the X86 release of the DEC BASIC PLUS compiler...
- ajross 3y agoFWIW those are all third generation "structured BASIC" languages, not what I understand the upthread commenter to be asking about. Obviously you can evolve the syntax into a more popular language, and Microsoft did to great effect. But that's not the BASIC that was "taught in school in the 80's".
- skissane 3y ago> FWIW those are all third generation "structured BASIC" languages, not what I understand the upthread commenter to be asking about. They weren't. Many minicomputer BASICs of the 1970s and early 1980s, such as Wang's, lacked those structured programming features you are talking about, at least originally. They were classic GOTO/GOSUB line number spaghetti code. And huge amounts of business software was written in them. Some of those apps still run today, because the languages have been ported to Windows/Linux/etc. And eventually, just like Microsoft did, they added a lot of those structured programming features. But sometimes you'll find pre-structured spaghetti-style code surviving long after the dialect gained the ability to do better.
- mypalmike 3y agoLots of commercial software was written mainly in BASIC. Plenty of games (a couple popular examples are Temple of Apshai and Questron, but there are certainly hundreds, particularly if you look at educational games of the 80s). And a lot of productivity stuff was written in BASIC, like database management (e.g. APX Data Management System - lots of the APX titles were written in BASIC), accounting (early versions of the very popular Peachtree accounting software), and even tax software (early versions of TaxCut).
- HeyLaughingBoy 3y ago> technically-savvy small businesses were buying Apples and PC's The outfit I worked for at the time sold directly into this area. We had a product line of simple I/O modules for physical automation (measuring temperatures, controlling motors, etc...) and all our programming instructions and examples were given in BASIC because it was on all computers and it was the one language that we knew everyone would be familiar with.
- rootedbox 3y agoIt's Turing complete.. and my apple II library had all sorts of crazy apps written in basic. I remember taking them apart when I was like 10.. and being like who has the time to write all these lines! Which.. I still think is crazy considering no IDE and how you would just input them line by line... leaving space between lines just in case you needed to put a new line in later.
- pan69 3y agoWhen using line numbers you wouldn't go from 1 to 2 to 3 etc, but from 10 to 20 to 30 so that you can always insert a line (e.g. 11) between 10 and 20. After a while when the numbering became to messy, you'd issue a RENUM command to renumber the entire program, e.g. RENUM 10 would make the first line 10, and then use increments of 10 for subsequent lines. At that point you start over by re-inserting new lines between the others.
- rootedbox 3y agothe good old days
- marssaxman 3y agoIt depends on what you mean by "BASIC". Nobody in that world cared much about portability or standardization, so the language had a protean quality; every vendor offered their own flavor, tailored to the needs of its platform. The variant you used may well have been a mere teaching tool, but there certainly were other dialects which served as serious application development platforms. I was a big fan of BASIC when I was young, and that led to spending the early portion of my career working on a series of BASIC compilers, all of them intended for complex software development. Two of them still sort of exist, in much-mutated form; one is now called "Xojo", and the other is Microsoft's rather-better-known Visual Basic.
- HeyLaughingBoy 3y agoRight. Still remember the day in college when I booted up my Radio Shack Micro Color Computer (MC-10) and someone exclaimed excitedly, "it has Microsoft BASIC."
- georgeecollins 3y agoVBA was used for tons of enterprise applications in the late '90s and early oughts. The implementation in things like Excel was surprisingly powerful and they had to sort of dial it back because they realized it was a huge security risk. (You could open up a spreadsheet that was a powerful virus.) In the '90s when we were developing a 3D game (in C++) I made an early iteration of the level designer in VBA on Excel. You would color cells in a spreadsheet and then hit a button, and the button would output a text file that told the game engine what mesh or object to put where. Terrible way to do it, but a great way to work fast in those primitive days.
- 7thaccount 3y agoPeople still use VBA all the time. I think of it differently than the basic language of the 80s or even the more powerful commercial compilers used by some today like PowerBasic. VBA is just so highly tied to Excel. There is a new way to also script Excel with some kind of typescript. It's built into the latest version of Excel and seems to be more straightforward.
- nxobject 3y agoAt this point, I think there are multiple sufficiently general-purpose languages bolted onto Excel if you have 365 (sadly enough, I work at a place with LTSC) - Power Query, the array language subset of Excel's formula language, Python, Office.js, VBA. But if you're collaborating with people I think you only predictably have VBA.
- HeyLaughingBoy 3y agoUgh! I still have nightmares about having to write the Validation procedure documents for a medical device production Quality system written in VBA/Excel. The program had started out as some scientist's desktop tool and somehow over the years, morphed into an actual production tool that now needed to be formally validated since we needed to make a change to it. Worst combination of spaghetti code and Big Ball of Mud that I've ever seen. I had the misfortune of being the only SW dev who was senior enough to do the task and who wasn't busy at the time, so I drew short straw! I shudder to think of the millions of dollars of product that have been shipped as a result of that code!
- TillE 3y agoExcept for some graphics code, Ultima I was written in Applesoft BASIC. Akalabeth was entirely BASIC, but that's somewhat less impressive.
- krumpet 3y agoI still play Ultima IV at least a couple times a year. Never gets old.
- MarkusWandel 3y agoBased on my limited exposure to "professional" software in the BASIC era... some pretty good stuff was a hybrid of BASIC and assembly language, leveraging the best of both (BASIC was pretty good at laying out screens, input fields etc, at least on the Commodore PET, whereas hand-coded assembly language had the code density and speed). Was it a "toy" language? Sure. I once implemented a non-scrolling toy spreadsheet program with it - just a fixed grid of cells - with some simple formula capacity and a manual "recalculate" trigger. Was that educational? You bet. Was it sophisticated? Not really. But I'll bet there were absolute tons of one-off business applications written in it. A simpler version of what Excel was used for later, and still is. And scientific calculations? If Fortran could do it, BASIC could. Until something better came along to replace both.
- MarkusWandel 3y agoAlso "awfully basic" compared to what? For me it was the first exposure to programming, period, and totally got me excited. Heck, back then even programmable calculators were exciting. There was just this hunger to program something, anything.
- reaperducer 3y agoWere there many complex programs written in BASIC? Or was it largely a teaching tool? People who weren't old enough to be in business remember BASIC as something from their home computers, but BASIC was integral to many businesses in the early years of general purpose computing. There were plenty of business programs written in BASIC, and part of its appeal was that any business owner with a little time could learn how to customize those programs to suit their particular business' needs. BASIC wasn't just for homes and home computers. Virtually every computer or computing device produced in that era had BASIC available for it, and for good reason. It was quick to learn, versatile, and when you knew the basics on one system, you could use that knowledge on other systems. BASIC was available on machines ranging from $250 to $200,000 or more. There wouldn't be BASIC on $50,000 machines if there wasn't a demand for it. My memory is a bit fuzzy on this specific, but I'm pretty sure that HP had a computer that came with both BASIC and AP/L. Nobody was using that machine in their homes.
- bombcar 3y agoI seem to remember some pretty serious (as in actual paid) programs written in QuickBASIC - the compiled version of QBASIC. Lots and lots of 'business middleware' was written in various forms of BASIC, the most famous being VBA, but also quite a bit in things like QuickBASIC in an older period. https://qb64.com https://qb64.com keeps the dream alive.
- satiated_grue 3y agoI was recently playing a commercial Atari game from 1981 called "Ricochet" that was written in BASIC, which came on a cassette. Atari BASIC stored its programs in memory using a tokenized format - it did syntax checking when the line was typed in, and then the tokenized form was stored to save memory. There was a table of variable names, indexed by token. So a quick and easy obfuscation technique was to overwrite the variable names with something like just carriage returns, so that when you LISTed the program it had no variable names and lots of extra line breaks. As I recall, at least. Haven't reinforced those memories in a while.
- magoghm 3y agoMAI Basic Four Inc. was a relatively succesful computer manufacturer that sold business computers that used BASIC as the development language for business applications: https://en.wikipedia.org/wiki/Basic/Four https://en.wikipedia.org/wiki/Basic/Four
- bitwize 3y agoMAI Basic Four was one of the business software platforms for small businesses in the 1970s. MAI sold it as a turnkey solution including the computer which was a rebadged Microdata 1600. It was almost a BASIC machine the way Lisp machines were Lisp machines: all application level code, including that used for system maintenance, was written in BASIC. The dialect was one of many called "Business BASIC", which basically extended normal BASIC with COBOL-like capabilities like better string handling, decimal math for currency handling, and ISAM-like file manipulation. It allowed for developing the same kinds of applications as COBOL while having a nicer development environment than COBOL. The major accounting suites for small business of the 1970s, MAS 90 and MAS 200, were written in Basic Four BASIC. A lot of applications were. Other dialects, like Pick BASIC, supported business applications as well. All of these were much more fully featured than like Microsoft BASIC on Commodore/Apple/Tandy machines. Those were toys in comparison to minicomputer BASICs. Basic Four itself shipped on some microcomputers like the Tandy 2000. Compatible environments came out for PC, including AB86 for DOS, Thoroughbred/OS, BASIS BBj, and ProvideX. Keeping those old systems running on newer hardware was an enticing business, just like for COBOL programs.
- emorning3 3y agoIn the late 1980's I rewrote a very large pension actuarial forecasting system, written in Fortran, to Basic. I'm very not sure, so I'm guessing that the system had several hundred thousand LOC. The idea was to stop spending a fortune on mainframe time and run pensions valuations on a microcomputer. The Fortran system, running on a mainframe, might take 60s to run a valuation. The same valuation would take a full day to run on a microprocessor, but it worth it because it reduced costs by a lot.
- lyk2005 3y agoI am curious how do you write software that takes a day to run. Today I can write line by line, and because computers are so fast, even "long" tasks complete/crash fast enough for me to iterate. I assume you had test cases but I still want to know.
- Jtsummers 3y agoDo you mean how do you write something that takes that long at all? By having data that takes that long to process. If you mean the actual accomplishment of it in general: 1. Get a subset of data that lets you create a representative set of test cases. You can validate your code in minutes, not hours or days. Then you run it on the full thing once you've seen that the 5-minute job works as expected. 2. Sacrifice a goat, pray to hopefully the right god, and hope it wasn't their son from a goat mother that you sacrificed. 3. Spend a lot more time thinking before doing. 4. Read a lot. (1) works if you can run the task on your own system or have access to a system to run it on. This is the best option, or some variation on it. (2) is unfortunately what happens a lot, they usually sacrifice the wrong goat and end up cursed instead of blessed. (3) and (4) are the next best option after (1), and should be done alongside (1) anyways. The system I'm on now is legacy and being upgraded. The test bed is available to me maybe 1 hour a week right now because everyone needs it and everything is urgent, apparently. I spent a lot of time reading the code, the documentation, and thinking about how to structure my solution to a problem our users have. My first pass validated the solution concept and took 3 days or so of thinking hard about the problem and 5 minutes of coding. The second pass is more robust (error handling) that took several more days of reading and thinking to identify what error cases could even occur, and two hours of coding. Yeah, if I could run it locally I probably could have finished it all in those first 3 days (honestly my 5 minutes of coding was figured out by the end of day 1, but I wasn't certain since I was new to the codebase). But when that's not an option, you spend more time thinking about the problem you're solving and the problems your solution will generate so you solve it before you run it in the first place.
- garfij 3y agoWe had a version of Bomberman that was written in some version of BASIC in high school (maybe QBasic?). It was great because we could hack on it to modify the game and immediately play with those modifications.
- HeyLaughingBoy 3y agoAt my first job, our order entry system was written in BASIC. The second version of the system was written in QBasic. I wrote lots of test and demo code in the language. We used it in all our manuals, since it was the one language that we knew our customers (mostly engineers and scientists) would be able to program in. I started writing a spreadsheet in BASIC, but never finished. I wrote a couple of simple games in it also. There are more, but I've forgotten about them. Now, if we expand the definition to include VisualBASIC, then the amount of production software written in the language explodes into at least 100,000 programs.
- boznz 3y agoGorillas ( https://en.wikipedia.org/wiki/Gorillas_(video_game) https://en.wikipedia.org/wiki/Gorillas_(video_game) )
- ykonstant 3y agoI wrote tons of cryptography and cryptanalysis code in a combination of assembly and BASIC on MS-DOS.
- JohnFen 3y ago> Were there many complex programs written in BASIC? I don't know generally, but I worked in housekeeping at a large hotel for a few years in my younger days, and the software they used to track the rooms was in interpreted BASIC. I didn't know that until my manager started cursing because the software broke. When I looked at the screen, the error message syntax was clearly that of BASIC. I just typed "RUN" at the prompt and everything worked again. She thought I was a genius.
- themadturk 3y agoI wrote a document management system in VBA for Word for a law firm I worked for in the late 1990s. Created a unique filename for new documents, stored and retrieved, maintained an index of titles, etc. We replaced it a year later with a much better system, but it was a valuable stopgap for something we desperately needed.
- fsniper 3y agoYes there were very serious software written in different Basic dialects. One that I was interacted with was a CAD software written in QBasic. It was about civil engineering and static analysis tool for concrete buildings. You could export projects to dxf format so you could import into AutoCad to fix bugs and plot. Funny how the name was MGCad and author insisted it stood for MegaCad. I suppose It was a nice coincidence that the Author's initials were MG :)