This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-07-12
Channels
- # aleph (5)
- # announcements (1)
- # asami (29)
- # babashka (2)
- # beginners (36)
- # biff (1)
- # cider (6)
- # clj-kondo (29)
- # clj-together (5)
- # clojars (21)
- # clojure (11)
- # clojure-austin (5)
- # clojure-czech (1)
- # clojure-europe (23)
- # clojure-hk (1)
- # clojure-italy (1)
- # clojure-nl (1)
- # clojure-uk (1)
- # clojurescript (38)
- # clojurewerkz (1)
- # cursive (10)
- # data-science (2)
- # datalevin (15)
- # datomic (8)
- # duct (5)
- # emacs (36)
- # events (4)
- # fulcro (7)
- # garden (1)
- # gratitude (1)
- # interop (4)
- # introduce-yourself (1)
- # leiningen (1)
- # missionary (3)
- # music (3)
- # nbb (4)
- # off-topic (21)
- # polylith (6)
- # remote-jobs (5)
- # shadow-cljs (19)
- # specter (4)
- # xtdb (4)
Does anyone have a nice client for working with your own github gists? Quite annoying that you can’t search or quickly browse through them on Github. Open to cli clients or emacs modes but haven’t seen anything too promising
Interesting. Still a little remedial. Was hoping someone had made a little TUI viewer that could list, quickly show the contents, etc.
I found <https://github.com/defunkt/gist.el>, but it looks like it might be unmaintained now
It is okay to hate defmulti
and defmethod
and think that they are a very high cognitive load on reading?
Although there is some frustrating tech out there (YAML 👀 ), I'm not sure hating on specific techs is ever a good thing. Maybe there's a tool approach, or mindset that can help.
I can understand disliking code that over-uses them or mis-uses them, but I don't think I feel the same about those constructs in themselves, sorry
@U7RJTCH6J is not about hating that I'll not need to use it or would dislike to use it, but the indirection gives me high cognitve load
multimethods solve the expression problem, if the logic you need to write doesn't have the problem it might seem like overkill but not any more then protocols.
it's polymorphic dispatch. Which is a fancy way of of saying you have a function (literately the defmulti) that dispatches to another function (the defmethod).
yeah I share this sentiment about multimethods feeling more complicated
It is probably good they are in core though as they are popular and codebases would probably include a lot of libraries with slightly different implementations of polymorphic dispatch
> compared to inheritance i love multimethods
Why not both? With derive
, you can have it 😄
https://gist.github.com/souenzzo/b00220ad5c2b65884f5ab792588be492
I would think that always is better to use something like map-dispatch-env
like in this case
Counterpoint: i think that map-dispatch-env
function is very bad and I would reject a PR containing it. The multimethod is clear and obvious, the mechanics of multimethods are well known and well documented, and the new function doesn't do anything new or compelling.
Seems like multimethods were a primitive try out to make a Type based dispatch in clojure and then they invented out protocols/records/reify for interop