Well - if you get another response requiring action, maybe the first email wasn't thorough enough :P

You lack basic reading comprehension:

https://edition.cnn.com/2014/05/20/showbiz/macklemore-costume-apology/index.html

This was a clear indication that Macklemore is not a good role model.

Also, you contradicted yourself just then and there. Not a single of your examples does string concatenation for these types. It's only JS

I worked (assisted with minor tasks) in a surgical room where those surgeries were done on a 15 minute cycle per eye. It's a fairly routine and clean thing for cataracts or frontal chamber lenses (like eye-internal glasses) when your own lens is still intact. Better thank Lasik for sure

You are entitled to your opinion. implicit conversion to string is not a feature in most languages for good reasons.

Why would you need an entirely different way of concatenating strings? "11" + 1 -> exception. "11" + to_string(1) = "111"

Executing after undefined behavior is arguably worse than terminating with an exception. A terminated script can't leak data or wreak havoc in other ways.

Thanks for saving me the typing.

Nor would I expect "1312" to equal "1213".. Still that operator with these operands should just throw an exception

BS. A language shouldn't have operators that allow non sensical operations like string concatenation when one operand is not a string.

TIL. I hope that evil fucker dies (of natural causes, but soon, please).