Daniel Chao

Yup, it definitely doesn't need to encode parentheses. It'd certainly be an improvement to not encode them here.

You can do this by declaring them as project dependencies. See docs here: https://pkl-lang.org/main/current/language-reference/index.html#project-dependencies By the way: package URIs should only have the version _once_ in their path, after the...

Something else you can do here is to deploy these assets elsewhere, e.g. to an S3 bucket (and then maybe CNAME'd so the url is shorter). Pkl doesn't actually care...

> According to the Javadoc, Executor "evaluates Pkl modules in a sandbox". Does preconfiguring with System.getenv() and System.getProperties() make sense here? And shouldn't granting file system and network access be...

The executor API is typically meant for services that need to evaluate 3rd party Pkl code. For instance, if you are a service that accepts Pkl files as configuration. And,...

Your setup here runs Pkl in the JVM, which means you're also incurring the time it takes for the JVM to bootstrap (e.g. it needs to load classes, fire up...

By the way there's also an in-language benchmark suite: ``` // abcd.pkl a { b { c { d = "Hello World!" } } } ``` ``` // benchmark.pkl amends...

The actual issue here is that we shouldn't be publishing an artifact called "pkl-cli". For the CLI, you want [pkl-cli-java](https://central.sonatype.com/artifact/org.pkl-lang/pkl-cli-java)

For those that are interested in implementing a python binding: we just published a specification for our message passing API, and our binary serialization format. Our documentation can be found...

What OS are you on, and what is your java version?