This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-08-27
Channels
- # aleph (1)
- # announcements (5)
- # babashka (13)
- # beginners (68)
- # brompton (7)
- # calva (10)
- # cider (1)
- # clara (15)
- # cljsrn (2)
- # clojure (63)
- # clojure-austin (1)
- # clojure-europe (44)
- # clojure-france (2)
- # clojure-nl (5)
- # clojure-norway (1)
- # clojure-poland (1)
- # clojure-uk (8)
- # clojurescript (8)
- # clojureverse-ops (7)
- # conjure (13)
- # core-async (27)
- # cryogen (10)
- # cursive (17)
- # datomic (13)
- # deps-new (1)
- # events (1)
- # fulcro (3)
- # gratitude (4)
- # helix (6)
- # honeysql (6)
- # introduce-yourself (1)
- # jobs (2)
- # malli (13)
- # meander (9)
- # music (1)
- # news-and-articles (2)
- # off-topic (8)
- # pedestal (1)
- # reitit (4)
- # sci (25)
- # shadow-cljs (13)
- # spacemacs (2)
- # tools-build (5)
- # tools-deps (20)
- # vscode (50)
- # xtdb (2)
I remember Rich mentioning in one of the interviews, can’t find which one but https://www.infoq.com/interviews/hickey-clojure-protocols/, something along the lines that if he designed Clojure again Protocols would play a foundational role in it. Can some elaborate what he might have meant?
That Protocols would be bootsrapped first and then instead of the extensive use of interfaces and native dispatch, a lot of core features would instead be based on Protocols?
Well you can see this in ClojureScript
Which was designed with protocols at the bottom and most of the abstractions are defined in protocols rather than Java interfaces
Nice, I’ll study the ClojureScript source in that case, have only been exploring the Java source until now
I have heard that the very first commits in the ClojureScript code base are instructive in this regard