I liked most of the LispOS paper. One point of disagreement is planning for multi-user capability. I don’t think a LispOS based system would ever be more than a personal and highly customizable workspace. I would never expect to fire up a VPS on AWS or GCP and see a LispOS option next to Linux, BSD, etc.
I used a Xerox 1108 Lisp Machine from 1982 to about 1986. I stopped using it and gave it to someone else in my company when I was able to port the ISI Grapher to Coral Common Lisp on my Mac and thereby was able to port most of my code over.
To be clear, I moved off of the 1108 only because the hardware had become outdated and it ran too slowly. Otherwise I was very happy with a single user all Lisp work environment.
Multiuser tends to go hand in hand with other things, like good security though. No doubt a modern single user system could avoid the mistakes of Windows etc. But as you're already going most of the way there, why not just build multiuser in from the start?
I'm sure Mr Torvalds never expected to fire up a VPS and have the option of Linux along side big and professional OSes like GNU and Unix.
I agree and wish an OS was turtles all the way down with extensive scientific computing builtin. How many layers of indirection do I need? I'm stuck on Windows so I have to deal with that, .NET, Python, and numeric software like Mathematica, as well as the 50 bazillion programs I use ...all with fragile interfaces. Maybe that only seems suboptimal though and a true LispOS and Smalltalk OS running on baremetal would never truly work with the general populace?
Been thinking about this a lot lately. What would a regular laptop user, say, or advanced user (office worker etc) need at a minimum to start using such a system? Probably just a functioning web browser and office suite. So long as any given LispOS/SmalltalkOS had those, and a working UI, I think it could actually work.
We have many more common and widely adopted standards now (XML formats, JSON, hell TCP/IP!) than we did back in the 70s and 80s when PCs were much more diverse and exotic -- and hence incompatible. Most things are compatible these days. This in theory gives us tremendous advantage when it comes to experimenting with new viable systems, don't you think?
The I/O boundaries and resource limits are the really important bits: A web browser is ultimately just a bundle of I/O functions buried inside specialized feature APIs, with only some very specific "patch this" limits for maximum resource consumption. This has allowed the size of web apps to creep upwards indefinitely while not being able to actually do every task, because the feature APIs sandbox in a haphazard "intended for the average consumer" way. When you add in comprehensive limits, the design and the software built on it are able to last: it's the lack of limits that has always created software crises.
One could imagine, instead of the browser as a lowest-common-denominator sandbox, a fantasy system specialized "for text editing", which has a different spec from one specialized "for 3D graphics": This would narrow the scope of sandboxing, make it easier to task-optimize, and yet also create the need for a Lisp or Smalltalk type of system that needs flexibility "for prototyping". It's not an unreasonable path, considering how broader trends in computing are leading towards hardware specialization too.
http://dspace.mit.edu/bitstream/handle/1721.1/36956/32890570...
Although, I think my default idea of a separation kernel plus (runtime/VM here) + (Camkes or Cap n Proto) for glue would work for LISP images, too. Throw in VLISP for as much component reliability as you get flexibility.
The AT&T lawsuit against BSD only came after that prohibition was lifted.
I (and many others) have been thinking about a system that boots to Emacs. With the guile backend we might get enough speed to make it tolerable fulltime.
The only thing missing (and I bet somebody has done this too) is a way to run graphical ELF binaries with an embedded X/Wayland type thing.
Buffers being graphical, including the possibility to work with images inline Lisp Machine style.
The gdb integration was more ergonomic, felt closer to something like DDD.