8 ms·
I can't escape the feeling that emacs got this right. Nobody wants their config to be lisp, but it fits the bill for what you needed. Especially combined with
by taeric 6y ago
I can't escape the feeling that emacs got this right. Nobody wants their config to be lisp, but it fits the bill for what you needed. Especially combined with the custom sections. So nice.
- remexre 6y agoYour config language being turing complete doesn't work if you need to accept/validate config files from untrusted parties
- taeric 6y agoWhile I don't disagree, you can get rather far by limiting what you allow in the evaluation. There is no reason you have to pull it in in your current environment directly. And then you have an easy mechanism to allow some configs from trusted parties to be a bit more capable, if they need it.
- contravariant 6y agoThough in that case you definitely want to disable macros for this config (as they allow for exponential time/space) and be very careful with any additional functions you expose.
- filoeleven 6y agoedn seems like the right solution, then. https://github.com/edn-format/edn https://github.com/edn-format/edn