Clojurians Log v2
aleph
Came across a statement by the maintainers that https://github.com/clj-commons/aleph/pull/723, which comes as a surprise to me since I’ve been a long time user and have never thought much about whether aleph is used by others or not (it works for me so why bother). Not that I’m going to change my stack just because I saw that thread, but I am a bit curious to learn what other options are there in Clojure land for wrappers/libraries on top of Netty if an application does need the high performance async IO that it offers, or if people like to just hand roll their own java interop these days
I use it in a custom stock trading application to do parallel downloads of financial information for maximum performance. Works perfectly for me.
I use aleph in development only as a webserver for my Datomic Ion application when I run it locally from a REPL. It's been great. Low maintenance, ideal surface area for my needs. I would not want to hand-roll something so I hope the authors keep it viable.
Using clojars downloads to judge usage is complicated. It is very common practice to use a private caching proxy maven repo
And vice versa, high download counts usually mean somebody's screwed up CI caching, not much else.
> I would not want to hand-roll something so I hope the authors keep it viable. Hi! As the current lead maintainer, I can assure you that we'll do so for the foreseeable future. At my company we're heavy users of Aleph in a mission-critical project (using the HTTP server/client as well as the TCP/TLS server/client components), so there's a vested interest in keeping it afloat 🙂
Just because my jars/docker images aren't rebuilt every day they're still running in prod just like they have been for the past 8+ years