(cover pic unsplash)
His take was that this is just fine, as Clojure is used by many for building apps (front and backend along with enterprise tools) - but it is very stable and therefore doesn't automatically generate "buzz" about itself... There are few changes to shout about and discuss.
There is indeed a lot to be said for an active community and the potential for an existing library out of the thousands to solve your problem very specifically.
As an example, perhaps the differences between Vue and React or Svelte (Angular and this or that) don't really warrant their on-going segregation of the resulting apps and dev communities? Is it actually, overall, less efficient and resulting in lower-quality apps over time?
(this might be a bad example, as I don't really want to discuss the merits of frameworks per se, but use their existence as an example that applies to npm in general)
I know that it can be argued that one or the other library/framework/whatever is better in certain circumstances than the others - but is that really true and do you really gain sufficient benefit compared to the effort of complicated build processes, maintenance, updates and on-boarding of new staff? Not to say the opportunity cost from barriers to knowledge sharing between teams using different libraries/frameworks regarding architectures and domain solutions.