Thought you'd like it. Came to mind again in a recent conversation on Ethereum with their "new" idea of distributed, smart contracts with programming languages. Reminded me of agent-oriented programming we did in the 1990's with products like Telescript running whole stores and stuff:
http://www.sce.carleton.ca/netmanage/docs/AgentsOverview/ao....
Impractical really, but fun concept. You created a bot that programmatically represented your goals, limits, heuristics for analysis, and so on. It could, with 1-2 commands, pack its code & data into a file that moved to another "place." It could move to Amazon's store over slow WAN, analyse certain products for you, commit to the right one, notify you, record the receipt, pack that up, and come back with a report for you. Used interpeters with safe programming languages and sandboxes plus A.I. for some of them. Imagine how easy, efficient, and secure Juice applets would be for that, today's smart contracts, or Facebook. Now you can sigh again as you realize how much faster and safer things could be if a handful of companies merely learned from the past and made it an option.
Btw, back then, we foresaw problems coming from untrusted or runaway code on machines in these agent marketplaces. So, platforms like Telescript had interpreters that isolated execution on a per-agent (per-user) basis. The platforms set in then-small datacenters on servers that spun up interpreters on demand in response to API requests. They measured CPU, memory, storage, and network usage for billing purposes. Any of that sound familiar? Like some "new" invention we hear about on HN, etc all the time? ;)