eekee wrote:
modulo my tendency to rebel against safe languages.
I find that interesting, because this is kind of at the centre of my vision. Without a runtime for the language, the introspection and integration kind of...don't work. Also, without runtime-enforced safety, you have to do traditional process separation for security, which seriously harms performance. (Unless you want to completely disregard security, which is a completely valid position.)
eekee wrote:
Also, I like the elimination of distinction between objects in different stores, but may very well have a filesystem-like object index, if that makes sense.
Yes. I plan something something similar. Every process gets its own 'namespace', but a namespace is just another object which has to reside somewhere. Think linux /proc, except all application-specific data is part of the app's 'proc'. So there's a root object of some sort (this part I'm not sure about yet; perhaps this can be configurable, so some people will have a hierarchical-fs type thing as root; others an array, or associative array, or database, or...—depends on personal preference). And then, before you can run a process, you have to give it somewhere to put its namespace. But you can also put other arbitrary data in the root (or subobjects thereof).
eekee wrote:
After failing at planning several times, I lowered my sights a bit, but I think I'll get most of the pieces in eventually.
Good luck! Incrementality is the way to do it.