The points in the article are pretty solid. But here is a big question. Imagine you can influence the switch of the configuration formats for projects like An

The points in the article are pretty solid. But here is a big question. Imagine you can influence the switch of the configuration formats for projects like Ansible, Kubernetes, Docker Compose, AWS CloudFormation, Google Cloud Deployment Manager, et al. You can take any project with huge user base and all of those project will have one thing in common: JSON-based configuration with an option to write this configuration in YAML. Since basically anyone talking YAML in the context of JSON is talking about a JSON superset. So here's the task: propose a JSON-compatible alternative to YAML. Things to keep in mind: - backwards compatibility - easy migration from YAML to a new format - full JSON compatibility - relatively cheap to get supported by the project of interest.