News for hackers. Stuff that matters.
Re:Why Clojure? (2010) by jeremiep on Friday December 30, 2016 @11:26AM (#13285149)
Ah my bad! :)

These look very much like Clojure's protocols and multi-methods.

Re:Why Clojure? (2010) by junke on Friday December 30, 2016 @11:41AM (#13285245)
Yes, more like multi-methods, except for standard qualifiers (:around, :before, ...) and user-defined ones. OTOH, Clojure allows you to define a custom dispatch function.
Re:Why Clojure? (2010) by jeremiep on Friday December 30, 2016 @12:41PM (#13285732)
Ah yes, Clojure has no first-class support for aspects. Its easy enough to monkey patch definitions for the rare case when its needed.

Most of the time however I try to avoid aspects as they introduce hidden behaviour in existing functions, which can be hard to reason about at scale, especially with more than a few developers.

Re:Why Clojure? (2010) by junke on Friday December 30, 2016 @01:58PM (#13286350)
I use them all the time. It's a great way to separate responsibilities.
Re:Why Clojure? (2010) by jeremiep on Friday December 30, 2016 @04:10PM (#13287478)
I prefer function composition for that when possible :)

Aspects I feel are more useful when you want to modify the behaviour of existing code you don't own.

Maybe if I had easy access to them I'd find more use cases :)