4 ms·
While a turing-complete language can be nice for document creation, it is a bad choice for document interchange. It opens up clients to abuse, because rendering
by layer8 4y ago
While a turing-complete language can be nice for document creation, it is a bad choice for document interchange. It opens up clients to abuse, because rendering/evaluating a document now requires performing arbitrary computations. It also tends to push computations to the client/receiver that would be more efficiently performed once by the server/sender. So one needs a “dumb”, non-turing-complete document format for interchange.
It’s easy to make everything a Lisp. What’s more interesting, and more challenging, is how to create expressive and expedient interchange formats that don’t turn into programming languages.
- martyalain 4y agoYou are right, the danger is there. It's up to everyone to reduce the power of the special forms - here [lambda, def, if, let, quote, macro, style, script, require] - depending on the level of security required for the wiki. A good compromise between unlimited document creation and secure document sharing. Same thing concerning the choice of server or client for page calculation, personally I like the idea of offloading the former and loading the latter, the server being only a remote neutral storage. And you can instal the server inside your computer, it becomes a local application, you will be able to share dumbs file if you want.