Even having any type coercion is a huge mistake. A true/false shouldn’t accept 0 or “false” with quotes or False with a capital f. It should be true or false. A

Even having any type coercion is a huge mistake. A true/false shouldn’t accept 0 or “false” with quotes or False with a capital f. It should be true or false. A single line string should accept one kind of quotes and one way of escaping. Similarly in xml it’s a curse that <Foo><Bar>1</Bar></Foo> and <Foo Bar=”1” /> are semantically the same but considered different in most systems. Just avoid ambiguity and make it impossible to face a choice. The same semantic meaning should have one expression.