You can say that for everything, after all if it's turing complete you can do anything. But practically, the difference is intention, which drives design and e

You can say that for everything, after all if it's turing complete you can do anything. But practically, the difference is intention, which drives design and ecosystem. E.g: starlark is very oriented toward idempotence and limiting side effects to get reproducible config data. By default they discourage reading files: https://github.com/bazelbuild/bazel/issues/13300 https://github.com/bazelbuild/bazel/issues/13300 But rhai is not particularly oriented toward config, and the doc promotes an extension to read files: https://rhai.rs/book/lib/rhai-fs.html https://rhai.rs/book/lib/rhai-fs.html The tutorials, stdlib, language design anf tooling will all reflect this. You probably don't want to use starlark to automate much action, but it will be well suited to describe states.