4 ms·
As a nostalgic trip, a little over 30 years ago I was playing with Randall Beer's LISP interpreter which ran in MS Basic on a TRS-80 model III, very slowly, as
by VLM 13y ago
As a nostalgic trip, a little over 30 years ago I was playing with Randall Beer's LISP interpreter which ran in MS Basic on a TRS-80 model III, very slowly, as seen on page 176 at this link (this is the first in a multiple article series)
https://archive.org/details/80-microcomputing-magazine-1983-03 https://archive.org/details/80-microcomputing-magazine-1983-...
I distinctly remember as a kid it was very slow indeed, but interesting.
I got lost reading the ads. In retrospect, computing used to be a much more expensive hobby than it is today. Not just relative terms, but absolute terms. Then again, people are much poorer now, so its required.
Anyway, since 1983, he became a neuroscience prof and mentions his BASIC LISP on his homepage
http://mypage.iu.edu/~rdbeer/ http://mypage.iu.edu/~rdbeer/
The line numbers are not consecutive, but I think he's well under a thousand lines of BASIC, there just aren't enough pages of code in the listing to exceed that.
And yes, this was considered reasonable coding style back then. That is why this generation never shrank in terror at the sight of bad Perl code. Why yes, this is a bit hard to read, but I've certainly seen worse...
- Morgawr 13y agoSlightly related to the "let's implement Lisp on weird languages/platform" theme, here's awklisp, a project that apparently helped/inspired Dipert to write Gherkin: https://github.com/darius/awklisp https://github.com/darius/awklisp
- brudgers 13y agoIn 1983, the TRS-80 was a mainstream computer. BASIC was also a mainstream language - so was Assembly. Even a decade later, before the explosion of the internet, getting one's hands on a C compiler typically meant paying for a commercial implementation...probably on floppies and delivered over the shoe net.
- VLM 13y agoThis is true, but I think by the standards of the 2010s most of the defining characteristics of early 80s MSbasic would be considered really weird. Line numbers. Control flow exclusively by if/then and for/next. We Love GOTO (noobs probably don't know what a GOTO is or why some considered them harmful). No namespaces, everything was a giant global shared namespace where $T meant the same thing everywhere. No naming conventions for variables (like Hungarian or CamelCase). No one used revision control. No unit tests. No symbolic debuggers (they were coming, soon, and something like them existed for assembly, but this was 1983 and not-assembly). For better or worse, no REGEXes. No object orientation, pure procedural. Everything is in one file because quite a few people had no disk drive and relied on cassette tapes. Line editing was a little crude compared to modern vim/emacs and pretenders to the throne. No IDEs until Turbo Pascal and the like quite a few years later (Or was quickbasic first? Either way it would be a long time...) By modern standards MSBASIC is pretty weird.
- brudgers 13y agoBASIC is perhaps one of the less weird things about computing the early 80's. It was the high point for women studying computing in universities - well over a third of all computer science degrees were awarded to women: three times the ratio found today. [1] But more to your point, by the 1990's the idea that computer languages should be understandable by non-programmers with a reasonable education and a general familiarity with the principles of computing was dead. Think of CoBOL. If its approach hadn't been abandoned for the obfuscations of C++ and Perl, Eric Edwards wouldn't have written a book and gone on the lecture circuits to spread the gospel of ubiquitous language. There's a reason the unschooled learned HTML and PHP in the 1990's - they were accessible to moderately educated people and could do useful work in the same way that CoBOL and BASIC were by design. The TRS-80 ran a version of TinyBasic. The use of line numbers and GOTO allowed BASIC to run closer to the metal - GOTO 15 is an Assembly Language JUMP to the address of where ever the instruction on line 15 mapped by the assembler. Without it, BASIC would not have been such a successful path to a higher level programming language for serious programmers steeped in assembly language. GOTO is handy if you want to translate from Knuth's MIX without a lot of fuss. [1] http://en.wikipedia.org/wiki/Women_in_computing#The_Gender_Gap http://en.wikipedia.org/wiki/Women_in_computing#The_Gender_G...
- mikeash 13y agoMany older BASIC implementations are interpreted, and it looks like Tiny BASIC was as well: http://en.wikipedia.org/wiki/Tiny_BASIC http://en.wikipedia.org/wiki/Tiny_BASIC It's strange to look back and see just how popular virtual machines were at the time. BASIC typically used one, as did many other languages. Smalltalk is famous for using a virtual machine, for example. Microsoft's original Mac apps all ran bytecode in a virtual machine. It seems crazy, because these computers were already tremendously slow, relatively speaking, and adding a virtual machine makes it much worse. However, it was ultimately a useful tradeoff because these machines were even more limited on RAM than they were on CPU power, and using a virtual machine with bytecode that allowed for an efficient instruction encoding could save a lot of space. It doesn't matter how fast your code runs if it doesn't fit in RAM, after all.
- ams6110 13y agoIIRC, Borland Turbo C was available by the mid/late 1980s, and was not too expensive.
- FigBug 13y agoLong ago I wrote a Scheme interpreter using Prolog. It's a horrible mess because I had no idea what I was doing. https://github.com/FigBug/scheme https://github.com/FigBug/scheme
- RBerenguel 13y agoYou should see some code I have written to parse a few English grammar subsets... That is messy, your code is extremely clean!
- breadbox 13y agoI also took the time to type in Randall Beer's Lisp from 80 micro. In fact, I'm pretty sure that that was my first time accessing a working Lisp interpreter. (Mostly working, anyway. I think I had a typo that I never managed to track down.) Unfortunately I didn't really know what to do with it. I didn't really learn how to use Lisp until I spent several days trying to write Lisp programs in college, and finally started to understand the functional paradigm. But yeah, that may have been one of the longest magazine programs that I ever typed in.
- wfn 13y ago> since 1983, [Randall Beer] became a neuroscience prof and mentions his BASIC LISP on his homepage > http://mypage.iu.edu/~rdbeer/ http://mypage.iu.edu/~rdbeer/ Just wanted to say thanks for linking to this fine chap. He seems to have a cross-section of interests such that I can really relate to and draw from. In particular, some people here might be interested about the intersection of cellular automata theory and (what it has to say about) cognition, autonomous systems, etc. (see e.g. [1, 2]) This is one of his approaches to understanding dynamic systems and how coordinated bahaviour can arise in them. See his publication list, too. [3] Apparently formal treatments / approaches to autopoiesis have been developed for quite some time (currently recommended books seem to be from e.g. 1980 and onward.) Interesting indeed! :) [1]: http://pubs.cogs.indiana.edu/pubspdf/34233/34233_varela.pdf http://pubs.cogs.indiana.edu/pubspdf/34233/34233_varela.pdf [2]: http://mypage.iu.edu/~rdbeer/Papers/Beer2014.pdf http://mypage.iu.edu/~rdbeer/Papers/Beer2014.pdf [3]: http://mypage.iu.edu/~rdbeer/pubs.html http://mypage.iu.edu/~rdbeer/pubs.html