Really cool! I particularly liked your Python and SQLite demos. I find it interesting that you <i>started</i> with a through-the-web (TTW) editing loop, calling it a quine. While valid, the key weakness is persistance: TidlyWiki does basically the same thing, but saving your work is a headache because basically you need another headless server process to persist anything.<p>Personally, when wanting to do something similar[0], started with persistance, and of course this means files. Plain text files I can edit with my programmer's editor store and distribute using the file-system. This avoids the problem of having to recapitulate a programmers editor in the browser, which is non-trivial. In turn you have the problem of writing a fast server, but that is a rather fun problem to solve [1]. You side-stepped the problem by using basic content-editable sections, but it is a huge problem, second only to persistence.<p>One thing I see you face which I also faced is the fact you cannot export things from inside embedded scripts! This would be a nice feature to avoid mangling the global window object. (It would also, in my use case, make code generation easier.)<p>0 - Literate Markdown: <a href="https://simpatico.io/lit.md" rel="nofollow">https://simpatico.io/lit.md</a><p>1 - Reflector, what I call the small node server that transforms, zips and caches your markdown, with a filewatcher invalidator: <a href="https://simpatico.io/reflector" rel="nofollow">https://simpatico.io/reflector</a>