LambdaMOO was(is) like this. And even more literally than in Smalltalk. Persistent objects, object oriented programming language, live code editing, object manipulation, programming right in the world, with immediate and shared effect.
But unlike a Smalltalk environment, the things you were editing were (in metaphor at least) living narrative "world" objects like rooms, objects, characters, etc. meant to give a (text-based) "VR" aspect. And it was multiuser, so collaborative.
It's a compelling, though exotic, way of making things.
If you'd like to literally live, breathe and walk around inside of your programming environment with your colleagues, set up your own https://dynamicland.org/ :D
Every time I look at one of their demos, I want to cry and say "I want this to be real". And then years pass, and there's another demo, and I'm re-reminded. This is more than vaporware, to be sure. But it's still nothing I can use in my day-to-day. Yes, it's research. It still makes me sad to see a possible future but no clear idea as to when it could become real.
So... I just did a little reading. And, I get the impression that if you want to do what I was suggesting, you'd have to physically walk up and talk to Brett Victor about it. https://dynamicland.org/2024/Is_Realtalk_open_source/ The entire goal of the project is in-person physical interaction.
The open nature of the environment led to data loss and corruption: crashes or forced restarts corrupted the Squeak image, faulty email synchronization scripts deleted server data, ad-hoc scripts sometimes created incomplete Person instances. The authors identified the need for transactions, backups, and crash recovery features. Storing all objects in memory limited scalability. And there is no mention of "performance" in the whole paper.
"Our observations are derived from an experienced programmer using a Squeak/Smalltalk image as the primary environment for carrying out everyday tasks over a period of eight months."
> experienced programmer
So not actually an example of "knowledge workers themselves should ideally be able to quickly adapt the software tools."
At a glance I'm not totally sure I see if this is qualitatively different from "living in the shell." I definitely find myself spinning up new tools constantly, but they're usually in shell or Python, not Smalltalk.
Whatever the waxing and waning that Smalltalk has had over the years, it's going to wane big time unless it can incorporate AI coding into their environments. Coding without it is going to seem ancient, soon.
LambdaMOO was(is) like this. And even more literally than in Smalltalk. Persistent objects, object oriented programming language, live code editing, object manipulation, programming right in the world, with immediate and shared effect.
But unlike a Smalltalk environment, the things you were editing were (in metaphor at least) living narrative "world" objects like rooms, objects, characters, etc. meant to give a (text-based) "VR" aspect. And it was multiuser, so collaborative.
It's a compelling, though exotic, way of making things.
I'm attempting to defibrilate the whole thing here: https://github.com/rdaum/moor
Everyone can try the Medley Lisp machine in the browser today! https://interlisp.org/project/status/2024medleyannualreport/
For a second I thought it had been ported to wasm! This is still a browser based VNC
http://wasm.interlisp.org/medley.html
This is excellent
If you'd like to literally live, breathe and walk around inside of your programming environment with your colleagues, set up your own https://dynamicland.org/ :D
Every time I look at one of their demos, I want to cry and say "I want this to be real". And then years pass, and there's another demo, and I'm re-reminded. This is more than vaporware, to be sure. But it's still nothing I can use in my day-to-day. Yes, it's research. It still makes me sad to see a possible future but no clear idea as to when it could become real.
Can you actually run your own Dynamicland? I couldn’t find any info about that easily on their website
So... I just did a little reading. And, I get the impression that if you want to do what I was suggesting, you'd have to physically walk up and talk to Brett Victor about it. https://dynamicland.org/2024/Is_Realtalk_open_source/ The entire goal of the project is in-person physical interaction.
That was the same impression I got, which makes sense for the project I guess. I just hope it gets big enough to be closer to my neck of the woods
Thanks for the heads up, this is a great update, I haven't seen Bret Victor's content in a while.
(2017)
The open nature of the environment led to data loss and corruption: crashes or forced restarts corrupted the Squeak image, faulty email synchronization scripts deleted server data, ad-hoc scripts sometimes created incomplete Person instances. The authors identified the need for transactions, backups, and crash recovery features. Storing all objects in memory limited scalability. And there is no mention of "performance" in the whole paper.
"In our environment, we implemented a central persistence mechanism called soup ..."
If only there was some decades old persistence implementation...
https://gemtalksystems.com/small-business/gsdevkit/
Oh!
You can already do this using Emacs with EXWM. I've been living this way for years.
Good ole M-x butterfly
"Our observations are derived from an experienced programmer using a Squeak/Smalltalk image as the primary environment for carrying out everyday tasks over a period of eight months."
> experienced programmer
So not actually an example of "knowledge workers themselves should ideally be able to quickly adapt the software tools."
At a glance I'm not totally sure I see if this is qualitatively different from "living in the shell." I definitely find myself spinning up new tools constantly, but they're usually in shell or Python, not Smalltalk.
Whatever the waxing and waning that Smalltalk has had over the years, it's going to wane big time unless it can incorporate AI coding into their environments. Coding without it is going to seem ancient, soon.
This is just a "lisp image", right? [with the attendant pros/cons ...]
Smalltalk for their paper, but yes. Same concept.
Nice to see a relatively modern paper (2017) focusing on Smalltalk.
a.k.a. Emacs.
[dead]