A Reasonable Configuration Language

Re:A Reasonable Configuration Language by gary_0 on Sunday February 04, 2024 @12:59PM (#39252596)

I wonder if anyone would take me seriously if I suggested WASM as a configuration language. When run, the WASM would be given imports that provide a small API for manipulating the config DOM, and importing and executing further WASM files. Then you can use whatever high-level config language you want (or, say, a subset of Rust) and compile it to WASM.

Existing JSON/YAML/etc could be compiled to WASM that simply builds the corresponding DOM.

Funny joke?

[ Parent | on HN ]

Re:A Reasonable Configuration Language by coderedart on Sunday February 04, 2024 @02:14PM (#39253370)

using wasm goes into crazy territory imo. It would probably be bigger, and opaque, with no proper errors (unless you compile debug info which would make it much bigger).

I think we already have an almost perfect language i.e. Lua Everyone knows it (or can learn it easily). tiny runtime to embed. sandboxed by default. garbage collected. Only feature missing is static typing.

[ Parent | on HN ]

Re:A Reasonable Configuration Language by viktree on Sunday February 04, 2024 @06:32PM (#39255645)

I think this is what the zellij terminal multiplexer uses for extensions.

It's worth mentioning that in the opposite direction, if you wanted to have an interpreted config option with fewer compile steps, there's also the option to use lua — a language for which the compiler itself is quite small and portable

See,

[1] : https://zellij.dev

[ Parent | on HN ]