go-jsonnet

You only looked at the pseudo version and missed the important replace directives replace github.com/candiddev/shared => ./shared replace github.com/google/go-jsonnet => github.com/thequailman/go-jsonnet v0.0.0-20230924031349-110b4ca1dc1a The replacement with ./shared means it's using exactly the version on disk (which is in a submodule here). The go-jsonnet replacement points to a specific commit.

> 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...

Not mentioned is the official GoLang version of the Jsonnet compiler. https://github.com/google/go-jsonnet In my experience the Go version is 10x faster than the original C++ implementation due to improvements. The only thing missing in the Go version is the formatter.

How many folks are familiar with http://jsonnet.org/ - there are two implementations: - One in go - https://github.com/google/go-jsonnet - One in C++ - https://github.com/google/jsonnet AFAIK, ksonnet is the primary user - https://ksonnet.io/ - which to any ex-googler be the more familiar way of dealing with the borg configs. HJSon seems nice, as once in a while how to put a comment in JSON comes, and everyone starts bike-shedding their favourite solution, that leaves lots questions... of compatibility. For example, we tend to use "_comment": "", but I know that's bound to break somewhere, soon or later. There is also https://json5.org/