Perhaps see my reply here (https://news.ycombinator.com/item?id=27654225 https://news.ycombinator.com/item?id=27654225). I think you may be misunderstanding wh

Perhaps see my reply here (https://news.ycombinator.com/item?id=27654225 https://news.ycombinator.com/item?id=27654225). I think you may be misunderstanding what is being stored here. Now as a caveat I'm not familiar with this language, but I am familiar with the concept as described. They are not removing source code, rather source code is stored after some processing; in this case it appears to be after lexing, parsing, and type checking. I'm not sure exactly what is being stored, i.e. an AST, but it sounds like they're basically moving this stage of compilation/interpretation to be much earlier in the process. I'm assuming this database can be queried and the result can be rendered back to a textual presentation as well. Presumably this opens the door for syntax being divorced from language semantics since how the syntax is parsed into the database and how the database is rendered into text can be a client side decision rather than set in stone inside the compiler/interpreter. What is set in stone is the semantics of the database that everyone must agree to. Again, there's the caveat that I'm not familiar with how this language in particular is implementing this concept.