This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-25
Channels
- # aws (2)
- # aws-lambda (2)
- # beginners (95)
- # boot (47)
- # cider (13)
- # clara (5)
- # cljs-dev (36)
- # cljsjs (9)
- # clojure (51)
- # clojure-austin (1)
- # clojure-greece (25)
- # clojure-italy (4)
- # clojure-japan (10)
- # clojure-russia (13)
- # clojure-spec (61)
- # clojure-uk (25)
- # clojurescript (26)
- # core-matrix (5)
- # cursive (8)
- # data-science (7)
- # datomic (43)
- # dirac (2)
- # emacs (8)
- # events (3)
- # fulcro (17)
- # graphql (29)
- # jobs-rus (4)
- # lambdaisland (4)
- # lein-figwheel (3)
- # leiningen (60)
- # luminus (15)
- # lumo (8)
- # mount (3)
- # off-topic (28)
- # om (22)
- # onyx (115)
- # other-languages (6)
- # pedestal (5)
- # re-frame (41)
- # reagent (12)
- # ring-swagger (12)
- # shadow-cljs (127)
- # unrepl (27)
- # yada (5)
@cgrand clients as in "implementing clients" or "improving the unrepl blob to the point where clients can be implemented more easily"?
to my mind, the main unsolved problem ATM is how to implement rich client features like autocompletion, docs
where should they be located - in unrepl, in an unrepl plugin (what would those looke like?), or in the client?
that obviously ties in with client development
@pesterhazy I was thinking of 1/ updating clients to cover more unrepl features (string elisions, side loader) 2/ figuring out what are the pain points 3/ paving the way for autocompletion etc.
Btw elision could be leveraged for better error printing: we can collapse parts heuristics deem as irrelevant more agressively as information is not thrown out
@cgrand, 1-3 sound good to me
remote pair programming.... I'm not sure how unrepl would help with that (over something like tmux or regular screen sharing)?
you want to be able to see what the other person is writing as they are typing
Oh, I don't know for sure it lets two people type simulataneously. Still, I think the idea holds, basically a shared "terminal"
what could be hacked around unrepl would be to redirect all outputs (+ verbose echoes) to both sessions, so participants would still have their own input streams.
Unrepl hack-day announcement: https://gist.github.com/pesterhazy/9918c47550a99da45bd6c20d33500b61
Good luck with the hackday folks! I will try to pitch in if I can connect that day 🙂
@richiardiandrea great, we'll be here and maybe even open a Hangout / http://appear.in / ....
yeah an http://appear.in channel is going to be good 😉
@cgrand, ellipsis added. Unfortunately it doesn't expand when you click.