[protomyth]

> That morphed into application and OS containers. Basically. They're way better than anything agent-oriented programming had back in the day. Also more versatile. That's why you don't hear about them for that much anymore except fringe academia.

The applications and stuff that goes into containers has to be written in some language, and I think an agent oriented language might be more suitable for large programs than what we currently have. I really don't think they are better, just more in line with what we have now.

As I said, I'm not really interested in the expert system aspect (AI). I'm looking at this as a language issue to build big systems. I think containers are not a language answer but a coping mechanism for current languages and practices. I've been doing research on a different path. I hope others are looking beyond what we have now and what paths history didn't take because C and UNIX won.

[nickpsecurity]

Most of what it takes to do that were just some interpreters and function calls. Originally established in distributed computing like Amoeba, MPP systems, and Obliq in agent-oriented systems. Might help if you think on it looking at distributed, agent, and reactive languages to see what language aspects you think would make it easier. Then you'll be able to convey it better.

To me, it's just a VM (or source), ability to capture state, and one or more function calls. Any language could do this.

Obliq just in case you didn't know about it:

https://en.wikipedia.org/wiki/Obliq