Interesting article. I show a bit of bias here where, in non-functional programming contexts, the ability to manage in the runtime via introspection/reflection is a characteristic I value.

The languages you evaluate are in the mainstream whether we like it or not. People change slowly. AND... there are reasons to use C# and Java... even if the reason to use Java might be Kotlin or Scala... ;-)

What I find frustrating is the flash-in-the-pan languages that purport to address key language issues that then get adopted, and the obligation of use translates in earlier days to awaiting the build out of frameworks and libraries and packages that bring a language up to speed so that we can do the same things we've been doing in one language in yet another. There needs to be a compelling reason to do this as language choice is not simply about language, it is about tooling, managing the technical debt in one place by ideally minimizing and eliminating it going forward in another.

I liked your article... and would add Lisp and Scheme just to be provocative... paren haters will writhe in anger, but the language constructs of so many of the languages you list have come from Lisp as well as Smalltalk (A Kay).

Best to you!