<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"><div>I'm wondering if you could easily put those objects into an RDBMS</div></blockquote><div><blockquote type="cite"><div>(trivially, you could, but you sort of want to preserve the schema in<br>that case).<br></div></blockquote><div><div><br></div></div></div><div>Well, it definitely is not :-p but those schemas are very "unstable" right now. There are still a lot of changes but we try to keep this document up-to-date.</div><div>What makes CouchDB (as database) so unique is that it is application server and database in one. So "obvious parts" of a world/part/module file can be omitted and Javascript/XHTML files can be created "on-the-fly" using CouchDB's Shows and Lists (<a href="http://wiki.apache.org/couchdb/Formatting_with_Show_and_List">http://wiki.apache.org/couchdb/Formatting_with_Show_and_List</a>) while writing changes/code to the database really just contains the "clean" code.</div><div>But a Node.JS server might to the same after querying a RDBMS...</div></div></div></blockquote></div><br><div>Besides that, storing a JSON serialization (worlds, parts) in a JSON-based (document-oriented) database makes it possible to do some analysis on those serialization (very easy with CouchDB), e.g. local code "extraction", reference/usage counting, ...</div><div><br></div><div>I still believe CouchDB has some extraordinary features that make it the right database (if any at all) to put source code/the Lively Kernel in.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Marko</div></body></html>