Let us review the progress we've had so far in this area * XML has the advantage of being almost perfect except its too verbose and isn't JSON * JSON has the

Let us review the progress we've had so far in this area * XML has the advantage of being almost perfect except its too verbose and isn't JSON * JSON has the advantage of being JSON, but is strangely broken at even basic stuff (i.e. comments, no trailing commas) * TOML has the advantage of being "better JSON", for people who like rust, but it is still too limited for a lot of scenarios * YAML is not as limited, but it has the advantage of giving bad people promotions and good people PTSD * HOCON has the advantage of being the goldilocks child of JSON and YAML, but nobody read the documentation * <YOUR PROJECT'S PL> has the advantage of being able to do anything and this is a disadvantage * Etc... for various reasons In all seriousness, I welcome Pkl! Configuration seems simple and I think another configuration language opens up a lot of pent-up frustration, but I am legitimately very happy to see some fresh ideas in this space. Incorporating a collection of typed records with a modicum of behavior and logic might be the secret recipe needed to crack the code. The fact that it can produce equivalent JS tells you that they've chosen a very intelligent subset of functionality of programming language features. My best wishes to the team!