Pavel Curtis is still out there, LinkedIn says he recently left his job at Microsoft after 20 years. He also runs a puzzle shop: http://www.pavelspuzzles.com/site/
I have some questions:
- Does each verb call create a whole new world state that it mutates, and later commits to the database? That's the impression I get from reading the code. Does this come with a lot of overhead? - What is that emacs mode you're using to edit verb code?
I've also wanted to give each object an isolated environment (make each one an actor), but I haven't thought too deeply about how exactly that would work and look. I've been planning in the back of my head to do this at some point in the next year, and was planning on implementing on top of the original codebase, but if there's a rust version, I'll use that.
I know it wouldn't be compatible with existing cores, but I'd be using it as the backend for a graphical ui anyway.
How did you go about converting the code? Did you just read through it, or did you start with a c to rust tool? I always thought the programmers manual and codebase were quite concise and readable.
One last thing, there were patches in the 90s to add journaling on top of the checkpoint system... Did those ever get merged into the main codebase?
Thanks for doing this! I'm excited!
Does it use async I/O / is it one thread still?
You might find this conversation interesting about multi-threading in LambdaMOO: https://groups.google.com/g/moo-talk/c/omF68ZM9rZc/m/B3f-jj4...
I hadn't looked at doing this in Rust yet, so it'll definitely be interesting to give the code a read, particularly with the focus toward modernization.
I also found this project randomly on github at one point, not sure how far along it got to being usable: https://github.com/verement/etamoo
telnet lambda.moo.mud.org 8888
A while back I wrote a MU*-style system in Ruby, using js as the scripting language. It has a web based tool that gives object owners a URL for each object, which lets them edit the attributes and code in a better way than just line oriented editing. It also lets external services call back to that object to trigger actions.
I never did anything much with it though.
Very fun. I expect the parallelism will also be strikingly better with a modern design and implementation!
I've had similar thoughts, so let me say "Congrats, this is awesome"! It definitely warms the cockles of my heart to see work like this. I just wish I had the free cycles to work on something similar (or even contribute to your project). But there are too many demands on my time right now. :-(
LambdaMOO Takes a New Direction (1992) - https://news.ycombinator.com/item?id=35856654 - May 2023 (15 comments)
LambdaMOO takes a new direction (1992) - https://news.ycombinator.com/item?id=22680965 - March 2020 (29 comments)
Lambda MOO Programming - https://news.ycombinator.com/item?id=20405167 - July 2019 (1 comment)
Lambda MOO Programming Resources - https://news.ycombinator.com/item?id=16327975 - Feb 2018 (1 comment)
Exploring 3-Move – A LambdaMOO inspired environment - https://news.ycombinator.com/item?id=14075439 - April 2017 (15 comments)
The "new direction" article was made famous by Clay Shirky in "A group is its own worst enemy". I won't list those here since it's a generic tangent but there are past threads at https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que....