duckscript VS rune

Currently i'm using it in cargo-make but will also use it later to parse args for duckscript commands.

At it's most basic you could make a really simple interpreter by just doing such a thing, and there is essentially already such a simple language like that built for/in rust called Duckscript (rust has a surprisingly large number of little embedded languages), and that would be completely and entirely sufficient for many purposes, though if you want speed then you'll need to JIT or AOT the code, which is why wasm is so handy as you can interpret or JIT (or even AOT it with wasmer) without the much larger overhead of a, for example, javascript or java embedded runtime.

There are a few research languages where handling secrets and constant-time operations correctly is a first-class feature. See for example:

https://github.com/google/rune

I can field questions folks might have on DataDraw. I'm not Bill, but I wrote the docs PR that recently overhauled the Rune README to highlight a lot of this interesting info about its use of the DD tool.

Another neat thing about DD -- the Rune compiler/grammar itself are written as DataDraw types, and one of the builtin things you can do is generate PostScript visualizations of them. Check this out:

https://github.com/google/rune/pull/33#issuecomment-13558283...

Maybe Google's new "Rune" language will become prevalent https://github.com/google/rune, which supports SoA.

The Rune Programming Language\ (99 comments)