So is JSON, and all mainstream config formats actually.
However, that stopped being a problem with JSON schema, which, despite the name, works on yaml too.
Blink. I beg your pardon, JSON is strongly typed per RFC 8259 standard:
> JSON can represent four primitive types (strings, numbers, booleans, and null) and two structured types (objects and arrays).
The type system does not align well with any other type system out there (float/int ambiguity, no timestamps, etc.) but it's still better than any coercion.
I fail to see what leads you to believe this is a relevant point when discussing INI files as the alternative to YAML.