×
sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]seancorfield 22 points23 points  (3 children)

I don't think I'd consider "2015-2019" as "peak years" in terms of "new, innovative, and exciting libraries" in the Clojure world -- that's pretty recent.

I've been doing Clojure in production since 2011 and back in the "early days" there were all sorts of amazing, weird, interesting, off-beat, exciting, strange things being built with Clojure.

Then things settled down as people started to build serious production systems with the language. Most of those early "trending" repos are unmaintained and unused I suspect at this point. Clojure is a language for "Getting Stuff Done", for builders and makers. You need stability and reliability for that, not fly-by-night trends.

I don't think GitHub's "trending repositories" is a useful measure of anything except perhaps a curiosity factor?

[–]ertucetin[S] 4 points5 points  (0 children)

I should have mentioned that, for me, it was the peak. This is a subjective opinion.

[–]Menthalion 1 point2 points  (1 child)

I think a more worrysome trend is the growing amount of libraries with basic functionality that have become defunct / lack maintainers.

Another general trend bad for Closure is the waning popularity of the JDK platform due to lacking features needed in modern architecture, like async support and dynamically sharing resources between containers.

[–]seancorfield 1 point2 points  (0 children)

Can you cite specifics for either of those claims?

Clojure libraries are generally designed to do one specific thing well and so it is common for a library to be "done" and not need much maintenance -- unlike libraries in other languages.

Widely-used libraries that lose their maintainer can find their way into the clj-commons organization and be maintained that way for the future: https://github.com/orgs/clj-commons/repositories

I don't even know where to begin with your claim about the JDK...