9 ms·
Many people who read about Lisp Machines are not aware that the InterLisp-D world and the MIT world (CADR, LMI, Symbolics etc) had significantly different appro
by gumby 4y ago
Many people who read about Lisp Machines are not aware that the InterLisp-D world and the MIT world (CADR, LMI, Symbolics etc) had significantly different approaches to how the systems should work, so even if you have read or used the MIT-style systems you will learn a lot by using Medley. I came from MIT out to PARC for a year, and later moved CYC from D machines to Symbolics machines (a complete reimplementation using a different fundamental architecture) so have good experiences with them both.
At heart, the InterLisp language itself isn't that different from MIT lisps, as Interlisp started down the road at BBN and there was a lot of cross fertilization in both directions. And CommonLisp, while heavily based on the "MIT" model has a lot of Interlisp influence in it.
But as far as the interfaces are concerned things are quite different. Writing code on an "MIT-style" machine was like writing it on the '10: type into an emacs and away you go. Interlisp-D's conception was heavily influenced by the SmallTalk experience: structured rather than text editing, mouse as a primary interface tool, and development based on images rather than files of code. It was much more intensely networked even than most computing today. Although I ultimately still preferred the MIT model, I learned a lot from Interlisp and there are many things I preferred in that environment. The most annoying part for me was the dependence on the mouse.
A nit:
> "The learning curve of such a complex system is steep, almost vertical."
This means you could effectively learn everything overnight. A shallow learning curve is the terrible one: takes a long time to learn.
- HexDecOctBin 4y agoIn common parlance, a learning curve is plotting effort/output, not output/effort. So vertical means nigh infinite effort to achieve small change in output. I also don't like this convention, since it flips dependent-independent variable dichotomy on its head, but it seems to be the widely accepted norm now.
- gumby 4y agoPeople adopting specific jargon (random, cloud, quantum) without understanding in order to try to pretend to belong. Sigh. Humans are complex. Worst example to me is the common use of the “ugly American” — in the book, he was the good guy who got out there and got dirty, as opposed to the pampered ones who stayed in the green zone, didn’t know any locals, and assumed everything in whatever country they were in was the same as in the ol’ USA, but just broken or corrupt. I’m not American but I always cringe when I hear this usage. Why do people have to hollow out metaphors, destroying language in the process?
- _a_a_a_ 4y agoTry climbing. I've done a tiny bit. It's hard going straight up as opposed to a nicely sloped walkable path. Takes a lot of effort. Metaphor WFM anyway.
- _a_a_a_ 4y agoCould you elaborate on the 'much more intensely networked' bit please.
- gumby 4y agoI replied to a comment by lispm which was a parallel comment to yours. Interested in your thoughts.
- pamoroso 4y agoI'm the author of the linked post, thanks for sharing your experience. I'm curious what you preferred of the Interlisp environment over the MIT world.
- galaxyLogic 4y ago> images rather than files of code This is my pet peeve about Smalltalk and I love Smalltalk. Image basically means a single huge file. It's fine if the IDE lets you navigate inside it when you are working alone. But with multiple authors the issue becomes how do you merge two or more huge files. Within a file all parts of it must work together. If you have a huge file the number of pairs or parts which must work together is exponentially larger. So merging "images" together is a problem on a class of its own.
- EdwardCoffin 4y agoThere were source code management systems, like ENVY, which made this easy. More than easy, IBM Smalltalk with ENVY was the best system I've ever used for collaborating with other programmers.
- galaxyLogic 4y agoI used it. It was great especially when you collaborated with other people in the same project who used the same Smalltalk base-image. But things got tricky when different people use different base-images and it is so easy to create new base-images. When you depend on (specific facts about) your base-image you don't need to declare such dependencies anywhere. Combine that with dynamic typing of Smalltalk. Then when you try to move to a different Smalltalk things just don't work and it takes time and effort to figure out why. I guess the way to do it would be to never save your image, but that is so easy and convenient. But if you never save your image, it is as if you are not using the feature of having the "image", so you can't really say it is a good feature if you never use it. When you do image-based development it is hard to control what and how many dependencies you create that are dependencies on the image you are currently working in.
- EdwardCoffin 4y agoThe way it was handled in my experience was people working on a specific component had someone rebuild the base image they derived their work from periodically, using definite versions of components from other groups. So a group writing one particular part of an application would periodically receive new images containing set versions of infrastructure components and peer applications. Older images would still work of course. Individuals could take those images and substitute specific newer (or older) versions of packages as needed. But definitely groups working on different things mostly only shared things that had been versioned in the shared repository. It seemed to work ok to me.
- lispm 4y agoI didn't use Interlisp-D systems back in the days. I was as a student only a short time (mid 80s) in a lab which had probably a dozen or more of them, incl. server and laser printer. They were already no longer being used. The lab at that time was for a research project for a natural language dialog system - think Siri without spoken language - the research prototype was about hotel room reservation dialogs. I'd think the main problem was the underpowered hardware - especially the small address space (both for main and virtual memory) - which was too small for the more challenging Lisp programs and their data. Users moved to Symbolics and also very quick to UNIX based Lisps on SUNs. > It was much more intensely networked even than most computing today. I'd like to hear more about that... what was it like?
- gumby 4y agoPARC's environment was a LAN environment, so printing (laser printing!), file storage, mail, and many other services were provided as cloud services by the network. This was in the late 1970s! Because the D machine environments (Smalltalk, InterLisp-D, Cedar/Mesa) were hermitic (you booted a machine with specific microcode for each environment and then the environment ran on the hardware) basically there were three different OSes that needed to support the common services. So the service implementations were smart: located via what was essentially an anycast and contacted via RPC. Everybody needed a client (for mail or whatever) but the implementations were easier. The MIT style machines were of course networked and rarely had, say, a local filesystem either, but those services were typically provided by a host (typically a PDP-10): basically a client/server model. The D machine environments just treated the (LAN of course) cloud services and not much different from any other local resource. It was easier to write and run shared services in those days than to use websockets today. Years later when I first encountered a Sun-3 I was shocked to discover it included an entire copy of sendmail and needed it to get the user's mail of the workstation! What an incredibly primitive approach, worse than I had had access to a decade before. Of course that crappy model survived, but the apparently dominant model of (say) reading your mail is even more retrograde: gmail is just you logging into a remote computer and running a modern version of elm on it to get your mail. In the late 70s D-machine environments you grabbed an object (e.g. mail message) frm the network, maybe presented it to the user, then used it in a reply, and cast it into the void for someone else to take care of. None of the modern siloing which simply recapitulates the worst part of the PC era.
- pjmlp 4y agoAnd Mesa, Mesa/Cedar were heavily influenced by Smalltalk and Interlisp, there are a few references that they wanted to duplicate the development experience of those dynamic environments into strong typing environments.
- gumby 4y agoYes, and surprisingly successful! It's a shame that passed away. Exploratory programming environments had their own "winter" and are only starting to return. That return involves a lot of recapitulation of old hard-earned lessons, because in CS it's considered poor form to read the literature.
- pjmlp 4y agoI don't know if it is CS to blame, or all the fashion trends that pretend they are showing something that will change the world from a couple of people creating start-ups without having had a solid engineering degree. One of the reasons I like digital archeology is the way my degree was all about regarding computing evolution subjects, and we had a proper campus library to go along them, e.g. most published Xerox books.
- gumby 4y agoThe weirdo "startup culture" that developed in the dot com boom and survives today is just a modern phenomenon. I remember a relatively high level of disregard for the literature even back in the early 80s, more in industrial research labs than academia of course, but even in academia the CS culture was quite different from the other sciences like mathematics or physics. Perhaps it was the engineering influence. It's peculiar as so much early CS came from people trained as mathematicians.
- 082349872349872 4y ago> I suppose the picture of computing is of a topsy-turvy growth obeying laws of a commercial "natural" selection. This could be entirely accurate considering how fast it has grown. Things started out in a scholarly vein, but the rush of commerce hasn't allowed much time to think where we're going. (a statement as true in 2023 as it was in 1963?)
- Abraham229 4y agoAm ready to learn with you I want to be you