FishFace

Presumably every so often there's a dispute because 0 + (0.3 + 0.3 + 0.3) - 0.3 - 0.3 - 0.3 is not equal to 0 (in floating point arithmetic).

For some purposes, I'm sure they do. But I dunno if that's what's going on here.

Good luck running iOS that way

Weird that anyone capable of understanding "test suite" is incapable of understanding that LLMs don't make progress when not generating tokens

It's that LLM output looks like human writing, so it looks like they might be able to do anything a person can.

Nothing to do with tastes changing or anything

Getting it on the third guess is not the brag you seem to think, and I'm still not engaging with you on the rest.

I mean how can you define a sensible way to subtract Infinity from an array, or add an object to a string?

TypeError.

There are also various sensible ways, for example if you have an array of floats, subtracting Infinity from the array could result in an array of the same length as the original, with each value being negative Infinity. But in general inhomogeneous types should not be addable without careful thought to create a type system which is consistent and coherent. That is exactly what JavaScript did not do.

It doesn't "handle bad code gracefully"; it handles it in a way that's hard to reason about and hence hard to work with.

The way JavaScript defines it is predictable

You literally just failed to predict it, so I don't think there's any point continuing this conversation.

Operator overloading is a perfectly reasonable feature in a language to make use of and to assume works. If it is not going to behave sensibly, it should be an error, not nonsense, because having it work for strings but not other sequence types is surprising, and surprising is bad.

As I said, the fact that you didn't know the result means that JavaScript's type system is opaque and hard to understand. You might have understood that there are some things you "shouldn't do" but being hard to understand is a bad aspect of a language even if it doesn't prevent you from writing correct, good code.

By way of analogy, thing of a language which, like JavaScript, doesn't require semicolons, but they are accepted. Except, if you use a semicolon after the last statement in a block, that statement never gets executed. Your reply is like saying, "just don't use semicolons - they're not needed" instead of acknowledging that an element of the language which is prone to causing mistakes is bad design.

🙄

but saying you’re a Star Wars fan is basically meaningless now. And for people who proudly wore that mantle, through eyerolls and ridicule, that’s a genuine loss.

I remember explaining something similar to my partner (not about Star Wars) and about how this isn't about "gatekeeping" (though it can become gatekeeping) but rather about this loss. I can't remember exactly what it was about now, but it was some aspect of nerd culture that didn't exactly become mainstream, but rather morphed to become mainstream.

The people doing this are not behaving rationally. Asking "why..." is fundamentally misunderstanding