Daniel Chao

Hi, at the moment, TOML support is implemented via a package, rather than in the standard library. https://pkl-lang.org/package-docs/pkg.pkl-lang.org/pkl-pantry/pkl.toml/current/index.html You can render TOML via: ```groovy import "package://pkg.pkl-lang.org/pkl-pantry/[email protected]#/toml.pkl" output { renderer =...

We're working on it!

> Does Pkl have a comprehensive benchmark suite? If you want proof, that’s probably the only way. Not yet. We have some very lightweight benchmark tests, but we don't have...

There is an in-language [stdlib module](https://pkl-lang.org/package-docs/pkl/current/Benchmark/index.html) that we use to write one-off benchmarks when we want to test specific things when iterating locally. There's also the `bench:jmh` task, although we...

Here's a quick benchmark that might be a good starting point for comparison. Save this to a file somewhere, then `pkl eval .pkl` to execute the benchmark. ```groovy amends "pkl:Benchmark"...

Look like you're right; `--add-opens` is not needed :D

I haven't forgotten about this one. Will take a look when I get the chance.

In 0.25 (the current release), `pkl eval` will error immediately if the given `--ca-certificates` files are invalid. I missed this--in the current dev version, it will only fail when the...

You're right; initializing cert stuff takes quite a while. In particular, `CertificateFactory#generateCertificates()` takes ~160ms to initialize when passed a pretty standard cert bundle. I think that's expensive enough to justify...

> I think that accepting a directory makes sense both from a user perspective (can use a directory other than ~/.pkl/cacerts) and from an internal perspective (see "upsides"). For comparison,...