Announcing Prospero: a strongly-typed configuration language with Haskell-like syntax A developer has announced Prospero, an early-prototype strongly-typed configuration language with Haskell-like syntax that evaluates to JSON or YAML, published on Codeberg at codeberg.org/theinnerlight/prospero. Prospero's type system includes units of measure, as shown by an example where `prospero evaluate --to-json example.ppo` prints "3584 MiB" from a list of services with memory and replica counts, and it rejects non-structurally-recursive definitions with an elaboration error. The author positions Prospero against Dhall and Nickel and against generating configuration in mainstream languages such as Pulumi and Scala's sbt, arguing that arbitrary side effects and non-terminating code in configuration are "a category error," and recommends Dhall for anyone needing a mature, production-proven configuration language. I’m announcing Prospero https://codeberg.org/theinnerlight/prospero - a new configuration language with Haskell-like syntax that currently evaluates to JSON or YAML. For a good few years now, I’ve been investigating the space of configuration languages like Dhall and Nickel. If you have to write complex configuration when working with the likes of terraform or kubernetes, these kinds of languages can drastically reduce the amount of complexity you’re confronted with and the volume of repetitive code you have to maintain. Despite their perfect fit for the problem space, I’ve never been entirely happy with any of the language options already available: I’ve been hungry for more type system features and the powerful type inference that languages like Haskell have treated us to. Late last year, I completed a major infrastructure as code project in Pulumi. It offers another arguably compelling solution to a similar problem: generate configuration in a mainstream programming language. I’ve encountered similar ideas from time to time: Scala’s sbt is another one I’ve used a fair bit that does something similar, letting you write your project’s build configuration in Scala. These kinds of approaches are extremely powerful but they come at a tremendous cost in both the amount and the types of complexity you have to deal with in configuration. In my opinion, being able to write arbitrary side effects and arbitrary non-terminating code in configuration isn’t a feature, it’s a category error. So, I decided to try and build a language that meets all of my needs more precisely. Prospero has a type system that features: Here is a little taster: example.ppo measure MiB measure GiB = <1024 MiB data Service = Service { name : String , memory : Integer