If that choice becomes perceivable to anyone but the authors and maintainers of the language itself, I'd say that's a first class failing, isn't it?
The quality of a language should be a pure function of the language itself; the interpreter doesn't (or rather, shouldn't) enter into it.
+---------------------+
| Author's competence |
+-------+-----+-------+
| |
| |
+--------------+ | | +---------+
|Implementation| <-+ +-> |Product |
| language | |language |
+--------------+ +----+----+
|
+----v----+
|Language |
|quality |
+---------+
I am not weighing in here on what specifically the choice of Haskell, OCaml, or Go say about author's competence; I am simply addressing your point that the choice shouldn't matter at all—unless you are convinced that the knowledge of PL theory and design principles is uniformly distributed across all language communities.
Apparently reading papers from the past 30 years is a "huge academic bias."
I'd honestly be fine if it was implemented in Racket too.
> inability to come up with a usable language or at least there exists a negative correlation with those languages.
No one has ever actually offered me a substantive argument that Haskell is unusable. It always seems to be "well, I don't personally understand it, and that means it's unusable" Uhh okay.
The fact that it has a "let" keyword does make it "academic" to me. I'm fairly sure we can now have compilers that don't need such hints to be explicitly provided. Rust enjoys its let keyword so much they have a "If let" syntax.
Languages that use random punctuation without providing real benefit could also use a cleanup. Lua with ~= is a good example: Tilde in mathematics means "approximate". In C != means "not equal". So lua's designers can be accused of either never seeing C or deliberately choosing something different. Given that Lua is implemented in C they can't easily claim ignorance.
Archaic and awkward ways of expressing code shouldn't be propagated into new languages unless here is a clear benefit. Have a look at Erlang. Excellent overall but has lots of old warts from yesteryear you wouldn't want in a modern language. Eg look at its string syntax / naming rules. Now compare it to Elixir. Modern. Same VM.
Moving with the times is useful. Future languages shouldn't be adding debris everywhere just to be different.
(As a reader, it's also really nice to be able to see "there's a new variable being created here" at a glance. Ambiguity is a human problem as well as a computer problem.)