This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-03-23
Channels
- # bangalore-clj (5)
- # beginners (136)
- # boot (1)
- # bristol-clojurians (6)
- # cider (46)
- # cljs-dev (172)
- # cljsrn (35)
- # clojure (82)
- # clojure-china (2)
- # clojure-dev (9)
- # clojure-dusseldorf (1)
- # clojure-finland (15)
- # clojure-italy (54)
- # clojure-norway (4)
- # clojure-russia (6)
- # clojure-spec (19)
- # clojure-uk (61)
- # clojurebridge (1)
- # clojurescript (55)
- # community-development (23)
- # cursive (7)
- # datomic (19)
- # emacs (10)
- # events (4)
- # fulcro (108)
- # graphql (7)
- # hoplon (1)
- # leiningen (7)
- # lumo (14)
- # off-topic (68)
- # onyx (23)
- # parinfer (8)
- # portkey (40)
- # precept (11)
- # re-frame (5)
- # reagent (40)
- # ring-swagger (5)
- # shadow-cljs (58)
- # specter (5)
- # tools-deps (37)
- # unrepl (13)
- # vim (9)
- # yada (12)
Unravel and unrepl are mentioned in @val_waeselynck's new REPL guide: https://clojure.org/guides/repl/enhancing_your_repl_workflow
š 16
I should finish up the 0.3.0 release, it seems to be working for people
You mean it's not a protocol?
Unrepl may not be a complex protocol but a protocol nonetheless, I'd say. Or what else would you call it?
Iād rather read āunravel only needs a socket replā than āunravel uses the unrepl protocol"
š 12
As much as I like attribution, the cool part about unrepl is that it doesn't need mentioning
You should write a blog!