Thank you! Great idea about revisions, will definitely add this!
Regarding AI, I was thinking about this as well. Perhaps for feedback/reflection on your notes, or to summarize longer periods and look for behaviorial patterns over weeks/months/years. What would you implement an agent mode for?
I’m curious why they chose MDL rather than Lisp for it. Sure, it would have been ancient MACLISP or whatever, but why not leverage what was already in wide use at MIT at the time?
MDL is what was in wide use at MIT at the time, the PDP-10 era. The M in MDL is sometimes "MIT" in the various backronyms of what it stood for. (Mostly it was apparently just short for "muddle", a self-deprecating description.)
(Also, to be technically correct, these source files aren't even MDL, they are a further descendant called ZIL [Zork Implementation Language].)
It sounds like from what I've read MACLISP and MDL were side-by-side for a while at MIT and something of a department choice. MACLISP sounds like the serious effort and I read MDL as the "hip" or maybe rebellious upstart with a weirder sense of humor (it was called Muddle and spelled MDL to make it seem like an appropriately serious acronym), which would also make some sense that Zork originated in that allowed to be sillier language.
(Also, in reading other comments around here, I've learned there's a deeper connection in MDL to Scheme than I knew before, so I hadn't realized the Lisp/Scheme split even has ties to this "competition" of Lisp languages at MIT.)
Because Zork was written on the MIT Dynamic Modeling PDP-10. MDL was an important part of the software ecosystem on that computer, but Lisp wasn't. On the other MIT PDP-10 computers, Maclisp reined.
Was there any particular reason they did that, or was it just a random coincidence (that was the team that wrote it and the hardware they had access to was that particular machine and that particular machine ran MDL, otherwise, it would have been MACLISP)? Was there anything about MDL that helped with writing an adventure game?
MDL is also from MIT and supposedly stood for More Datatypes than Lisp. According to wikipedia "MDL provides several enhancements to classic Lisp. It supports several built-in data types, including lists, strings and arrays, and user-defined data types. It offers multithreaded expression evaluation and coroutines."
Seems that most of it's novelties were eventually added into LISP proper.
It’s very Lispy, but it’s not strictly Lisp. Why, for instance, use “<“ and “>” to surround various forms but not others? If they were to make a mini-Lisp, I’d expect something more like Gnu Emacs Lisp, something that’s obviously a Lisp, but heavily influenced by the Lisps of the day. I’ve found a few old MDL manuals linked from Wikipedia, but none of them have any sort of “Here’s why we created MDL” section that I could find.
Pebble was amazing! Whimsical, useful and a loooong battery life. Strangely, there’s no alternative on the mass market. Or there has been no alternative.
We’re also seeing super slow dev build times with Next.js. It takes around 12 seconds for the initial page and then 2-3 seconds for other pages.
I always thought it was an inherent issue in this app due to the many dependencies (9000+ modules for each page) but I’m going to try what the article suggests.
Does Rsbuild or any other build tool provide an alternative to Static Site Generation with automatic code chunking? Because this part of Next.js is great. The production app is super fast to load.
Bouquin looks like a very comprehensive tool, I'll give it a deeper look!
And I will definitely work on those improvements, they seem like must-haves w/o compromizing the minimalist approach I took.
Thanks again and all the best!
reply