Read the thread again, it seems you slipped somewhere. This was all about the claim that implicit conversion to string somehow could make sense.

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

C# is filthy. But it explains where you got your warped idea of righteousness.

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

I don’t think there’s a way to retrofit JS - but php versions are deprecated all the time. Why not do the same with client-side script versions? :)

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.

I am lobbing rocks at you because of that admission.

today I learned - using Linux at home since 2005ish and I have never had an auto-file generated on any USB attached drives of mine…

honestly - while a Mac is certainly less painful to use than winshit, putting rubbish files recursively into each(!!) accessed folder, on all thumbdrives ever inserted, that’s something Jobs deserves to burn in hell for.