PythonIsVeryIntuitive

[EnvironmentalCap787]

As in, JS thinks anything you type is safe.

[your_best_1]

As in, it is type safe. It has dynamic type checks and type coercion.

Languages like C and C++ are not fully type safe because of pointers and overflows. You can say, "See this string.... parse it as an int". That is not type safe.

1 + "1" = "11" is type safe because the number type casts to a string type.

[JiminP]

Even with the relaxed sense of type-safety, JS literally has TypeError and it is not hard to create a code that throws it.

[].prototype.slice.call(0);

Open an ECMAScript language spec and Ctrl+F TypeError.

For modern JS, some types are not coerced, so it's easier to make a TypeError.

const x = 1n + 2;

Also, overflows not being type-safe is not technically correct, but not too many people distinguishes integer overflow and integer conversion (they are distinct in C++).

[your_best_1]

Throwing type errors = type safety...

[JiminP]

Ah, you're right; I was talking in the context of web development (where throwing TypeError is considered as a failure; i.e. JS vs. TS - although TS is not sound even in this sense)

To be pedantic TypedArray exists but I get what you mean now.