The problem is that document, serialization and configuration formats are different usecases and need different languages. We learnt that XML was a bit too ver

The problem is that document, serialization and configuration formats are different usecases and need different languages. We learnt that XML was a bit too verbose for serialization and moved to JSON. Now we need a good configuration format, especially for the advanced usecases, and YAML ain't it. The known ambiguities are a minor thing - the real problem is that it's not typed enough and significant whitespace. We need a language optimized for custom datatypes. That's why properly used XML is actually better here (it's better typed), but it's far from optimal. We could really use a different option.