There’s two main reasons. The first is that programming languages are designed for programming, not cartography. Both types of work require different skillsets. I find it hard to focus on cartography when I’m working with programming languages.

The second is what’s involved in writing it in a programming language. To be of any use you need to build up utility scaffolding. Generally this takes the form of some kind of layer object that you apply properties to.

You can see this scaffolding in the case of versatiles, where I think they have more code to generate the style than they have code defining the style.

Eventually if you’ve built up enough scaffolding, your programming language starts to feel like a DSL. For a previous project I had to use Gatling for some load testing. With the way it’s written it feels like a DSL, even though a Gatling script is valid Scala.

Where to report problems with Shortbread schema itself? (Or suggestions what to add or change.) To the shortbread-docs repository?

Yes, changes to the shortbread schema should be reported in shortbread-docs.