cel-spec VS jaspr

My employer uses a combination of Protocol Buffers (for the config schema definition) and Bazel/Starlark (for concrete instantiations). Configs are validated at build time and runtime using CEL (https://github.com/google/cel-spec).

The Common Expression Language (CEL) implements common semantics for expression evaluation, enabling different applications to more easily interoperate. https://github.com/google/cel-spec

Looks like Google invented a specification for a simple "expression language." -> https://github.com/google/cel-spec/blob/master/doc/langdef.md. Writing the expressions feels like writing Java, C++, Go, or TypeScript code. Google then released C++ and Go versions of this langauge as a library.

https://github.com/google/cel-spec unfortunately, it's in Go or C++. Of course I can write a binding to them. But is there any other similar that you would know of for Java? My other course of action would be to offload computation to another service using this library in Go, or Jsonnet or Open Policy Agent/Rego based evaluation, which I'd prefer not to. Executing JS in Java via Nashorn also an option but it'd be heavy weight.

Having a standard way to share expressions does seem quite useful, especially when it's multilingual.

[0]: https://github.com/google/cel-spec

There's more information about CEL and its specifications here

Especially when dealing with more complex match rules, I personally much prefer Caddy's matchers over building some weird-ass if constructs in Nginx. It also supports CEL for request matching, giving you access to extremely powerful logic, if you need it.

I've been trying to invent a JSON-Lisp language like this for a long time. My first attempt was Jaspr (https://github.com/ar-nelson/jaspr), which has its own syntax that compiles to JSON. But I'm working on a new, Turing-incomplete variant called MiniJaspr that fills a similar niche to config languages like Jsonnet or Dhall.