How can you track complex information flow for an organization rapidly changing its structure and workflow?
To cope with this situation, we've been using a Lisp-based object oriented database (OODB) from the beginning of the production. Lisp's flexibility allows us to change internal data structures quickly while maintaining the compatibility with the other parts of the production, which turned out to be the key requirement for such a fluid structure.
Trying to clear the backlog of items from before the conference...
Shiro Kawai tells an interesting story about a database intensive project (we are talking terabytes here) implemented in Lisp. Another aspect of the design was using an open and well-defined scripting API, implemented (obviously) in Lisp.
If you find this interesting, do read the second article Shiro wrote about these issues.
Oleg, who pointed me in the direction of these articles, also suggested a comp.lang.scheme thread discussing these projects.
Posted to functional by Ehud Lamm on 6/25/02; 2:35:21 AM