This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-02-07
Channels
- # beginners (4)
- # boot (186)
- # cider (68)
- # cljsjs (2)
- # cljsrn (6)
- # clojure (103)
- # clojure-dev (1)
- # clojure-russia (117)
- # clojurescript (40)
- # community-development (31)
- # cursive (2)
- # data-science (7)
- # datomic (6)
- # devcards (2)
- # editors-rus (2)
- # emacs (2)
- # jobs (2)
- # ldnclj (2)
- # lein-figwheel (41)
- # off-topic (5)
- # om (50)
- # overtone (2)
- # re-frame (36)
- # reagent (1)
- # spacemacs (3)
- # yada (2)
Perhaps it would do good to conduct a survey to see where the majority vote lies at
Braid would probably continue regardless of whether clojurians are going to adopt it
@cfleming: currently it's somewhat functional, but definitely lacks the polish for mass adoption
@meow is proposing a talk at clojurewest on braid, hopefully to onboard more people to help with development/testing
@jethroksy: Right, I’ve used it a bit, it’s definitely a long way from a Slack replacement.
in order for it to be successful everyone must be familiar with it, if not chaos would ensue
they've become too used to the braid system, and need more people to provide feedback on "first-use" experience
either the control logic in the app has to be complex enough to handle all these cases, or the users have to be intelligent enough to know how braid works
re: necroing in Braid, there will be UI to indicate old threads and to warn user that they are necroing
re: # of people... there's only ever 3-5 people actively participating in a room at any given time (many lurkers)... I image more would actively participate in Braid b/c conversations are less time-sensitive than here