sjsonnet

> jsonnet seemed like a great idea to me, but I've experienced extremely low performance. Although each implementation of jsonnet has some quirks, take a look at sjsonnet^1 (scala-based) or go-jsonnet^2 for improved performance. We generally prefer go-jsonnet. There's also a Rust version^3 that claims to be the fastest yet^4, but I haven't experimented with it at all. [1]: https://github.com/databricks/sjsonnet [2]: https://github.com/google/go-jsonnet/ [3]: https://github.com/CertainLach/jrsonnet [4]: https://gist.github.com/CertainLach/5770d7ad4836066f8e0bd91e...

We make heavy use of Jsonnet at work (https://databricks.com/blog/2017/06/26/declarative-infrastru...). It's worked great. Having a hermetic, pure templating system whose only output is a set of JSON/YAML files means that you can refactor fearlessly: as long as the materialized JSON/YAML doesn't change, you are 100% sure your refactor is safe. Bazel's StarLark dialect of Python (https://github.com/bazelbuild/starlark) has similar benefits. The language is simple and remarkably well specified, enough that we implemented our own intellij plugin (https://plugins.jetbrains.com/plugin/10852-jsonnet) and even our own faster compiler (https://github.com/databricks/sjsonnet) without much effort at all. There are odd corners in the language, but not something that most people will end up bumping into in typical usage. The templates certainly get m

This can be somewhat mitigated by AOT compilation. Here's a link to some experiments from using SubstrateVM to create a self-contained executable from sjsonnet: https://github.com/databricks/sjsonnet/issues/2