It’s dumb because it can’t be reliably extrapolated to other instances.
It’s perfectly reasonable for someone to think Java and JavaScript are related. It’s not reasonable for people to think ham and hamsters are related.
This is a result of badly naming something because the ECMAscript creator wanted to ride the coattails of the ‘hot new thing’ at the time, which was Java.
For example, people shouldn’t immediately doubt whether Godot and GodotScipt are related because Java and Javascript are not. Your hamster analogy falls apart here because it only describes an exception, not a rule.
It’s dumb because it can’t be reliably extrapolated to other instances.
It’s perfectly reasonable for someone to think Java and JavaScript are related. It’s not reasonable for people to think ham and hamsters are related.
This is a result of badly naming something because the ECMAscript creator wanted to ride the coattails of the ‘hot new thing’ at the time, which was Java.
For example, people shouldn’t immediately doubt whether Godot and GodotScipt are related because Java and Javascript are not. Your hamster analogy falls apart here because it only describes an exception, not a rule.
It’s not my analogy.
Right… if you’re going to split that hair then you’re just proving my point.
I’m not splitting a hair, I’m just telling you I don’t feel that strongly about it because I’m not the one who made it. I’d never heard it before.
It doesn’t have to be the whole explanation. It’s not like you get a singular sentence to talk to someone lol.
No, even adding it takes away from the explanation for the reasons I mentioned.