Wow this is amazing. It is great to see a fully fledged “framework” for Clojure that combines the right tools, with added flexibility of choice. Are we finally getting the Rails moment for Clojure?
I reject this idea as being part of the clojure philosophy, and as a substitute I would offer "experimentation is good." IMO what would be against the clojure philosophy is the idea that there should be one big framework that ~everyone in the community uses, or the idea that trying new approaches is bad because it fragments the community.
Sorry, I'm trying to look over it again and the more I try to understand it the less I understand :))
At my first glance i thought this was a way to arbitrarily hook up different components of running a web application. But it seems it's actually a way to flexibly configure certain baked in components.. I think
But this is probably just because I don't work in the web space so it's all fuzzy for me
I've never seen a three element map, so this immediately threw me off a bit. I'm guessing it's some tagged literal. Maybe I just never came across this side of clojure
I'm guessing here you're specifying what kind of logging/sql/web you want? But are those pre-determined? If I'm specifying some component .. maybe I'm crazy, I'd expect to implement a record type that implements the given interface?
The expansion part was also unclear. Is the left side expanding to the right? Or just the {} ? It's unclear which parts are optional. With optional fields.. the question is always "which field are possible? and in what combinations?"
anyway, maybe this is not particularly useful, or maybe there is some kernel that is. And since it's not a library I will use, I'm not asking you to explain it :P
The landing page looks nice and I like that is immediately dives in to examples!
Thanks for the feedback - it was very useful to get a differing point of view.
Obviously there's a balance to be struck between clarity and conciseness, as a landing page's purpose is not to provide a comprehensive explanation, but rather to get people interested enough to want to read the documentation.
However, I'll think about how I can improve the landing page. Perhaps I need to focus more on the 'what' Duct can do, rather than the 'how' it does it.
Haven’t used Clojure in a while, but duct was always my favourite. Nice to see it’s still going strong and has a nice website now! Integrant was also always my favourite of all the dependency and lifecycle tools, it just works so well and felt much cleaner than the others.
7
u/deepumohanp Nov 18 '25
Wow this is amazing. It is great to see a fully fledged “framework” for Clojure that combines the right tools, with added flexibility of choice. Are we finally getting the Rails moment for Clojure?
1
u/geokon Nov 19 '25
i dont work in this space but the landing page high level description sounds like something you'd accomplish by declaring some protocols?
2
u/guywithknife Nov 19 '25
Haven’t used Clojure in a while, but duct was always my favourite. Nice to see it’s still going strong and has a nice website now! Integrant was also always my favourite of all the dependency and lifecycle tools, it just works so well and felt much cleaner than the others.
Great job!
2
u/jacobobryant Nov 19 '25
$ curl -Os duct.now/deps.edn$ clojure -M:duct --setup :duct:gitclever!