Maybe Go can claim to be simpler. But there are many runtimes that are popular and equally complex as nodejs.
I know, I’ll let myself out.
> 1/0
Infinity
> 0/0
NaNWhile `1 / 0` is not a valid operation, it can be interpreted using limits. If `x` approaches 0, then `1 / x` will approach `Infinity`, hence JavaScript's result of this operation.
But with `0 / 0`, there is no unambiguous interpretation, so JavaScript defaults to `NaN` as its indicator for when a number is expected, but not received in valid form.
I'm not defending this behaviour of the language, just pointing out that there aren't "two different ways" of wrong behaviour at display here.
I like this quote, it reminds me to another favorite of mine, the Sagan standard: "Extraordinary claims require extraordinary evidence"