And the idea that a language can be designed around one data structure is elegant. Of course you get that in Lisp and Smalltalk as well. But having all those primitives that work over array structures is incredibly expressive.
I believe the array podcasters when they claim array languages can be several times more productive than other languages, at least for domains that fit well with arrays.
At least mention prolog, forth, SQL or the like that are truly different.
(It is, however, difficult to disentangle some features that Rust’s ownership model requires but which aren’t necessarily a part of that ownership model: for example, algebraic data types are essential and expression orientation extremely desirable, but there are other languages which have those features without the rest of the ownership model.)
People often think memory safety without garbage collection is Rust’s shtick, but it’s actually the ownership model that’s Rust’s defining feature, underpinning everything and making that possible.
Lisp has its macros.
Elm has its type system.
Go, Elixir, and JS have rather idiosyncratic concurrency models.
Rust has its borrow checker.
Perl seems to be SO special that even proficient Perl devs aren't able to write performant code in it. /s
Sure, Prolog and SQL are much more different than the rest. But I didn't want to strawman here.