You mean such readable and understandable names like car, cdr, cadr, .... ? For the uninitiated, car is not about vehicles.
Clojure had a chance to do better because they were starting a new thing.
It's not necessarily a flaw with the language, in any case, just something I've noticed in Clojure articles.
I suppose I'm agreeing with the author - refactoring Clojure to make it more readable is a good idea.
And it did. The seq abstraction is way more practical than the old-school list obsession in other Lisps. You get to treat collections uniformly while keeping the performance benefits of each implementation. Pretty smart move, honestly.
While Common Lisp does have sequence functions, Clojure's seq abstraction is fundamentally different and more comprehensive: Clojure's seqs work uniformly across all data structures (vectors, maps, sets, strings, etc.), not just sequences; Clojure seqs are lazy by default; The seq abstraction is built around immutable data structures from the ground up; In Clojure, everything implements the seq interface - it's the primary abstraction, not just a library feature.
Common Lisp's sequences are more limited - they work on lists, vectors, and strings, but the interface isn't as pervasive or as foundational to the language design. Clojure made the seq abstraction central to how you work with any collection.