This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (1)
- # beginners (206)
- # calva (2)
- # cider (64)
- # cljs-dev (12)
- # clojars (2)
- # clojure (177)
- # clojure-europe (2)
- # clojure-finland (1)
- # clojure-italy (2)
- # clojure-losangeles (5)
- # clojure-nl (7)
- # clojure-russia (69)
- # clojure-spec (41)
- # clojure-uk (92)
- # clojurescript (60)
- # core-async (16)
- # cursive (48)
- # data-science (6)
- # datomic (73)
- # duct (5)
- # events (2)
- # figwheel-main (5)
- # fulcro (29)
- # hoplon (1)
- # off-topic (52)
- # pathom (11)
- # reagent (4)
- # reitit (5)
- # remote-jobs (1)
- # rum (7)
- # shadow-cljs (58)
- # slack-help (10)
- # spacemacs (3)
- # testing (3)
- # tools-deps (5)
Interesting blog post on switching from slack to spectrum - a lot of the criticisms of slack for public forums and community rang true for me: https://blog.apollographql.com/goodbye-slack-hello-spectrum-8fa6b979645b
> Apollo team members have been big Spectrum fans since its inception, not just because it’s using the Apollo platform (that helps! 😍), but also because its founders, Brian Lovin, Max Stoiber and Bryn Jackson, have been awesome Apollo community members. A little bias in place :)
Good call - looks like this subject has been breached previously, I should have checked first.
I would much prefer if people wrote questions in ClojureVerse instead. Forum answers can be vetted, refined over time, can be much more complete etc etc. We should promote that more.
First time I've checked it out - excellent forum, thanks for bringing it to my attention.
A community needs a real time chat platform, be it Slack... or IRC, a forum, Stack Overflow, reddit, etc
^ Agreed; there's clearly a place for both. I've been liking Zulip, and would happily make the move there if we could get critical mass. https://clojurians.zulipchat.com See also Sean Corfield's recent blog post on Slack alternatives for Clojurians: http://corfield.org/blog/2019/02/11/clojurians-slack-alternatives/
ha, interesting... https://github.com/clojurians/clojurians-chat/wiki
to get critical mass for a Slack-alternative it’s important to attract users for which Slack is not working - Slack is indeed popular but for a select group of users. For eg. local usergroups and smaller oss-projects the synchronous dynamics without option to search is not beneficial.
e.g. local usersgroups were on Slack but left: https://clojureverse.org/t/subcommunities-got-off-clojurians-slack/3172
I didn’t read the entire post, but an important question is: did those local user-groups succeed elsewhere? it’s really easy to create a channel for your user group/country and then not look at it again
"to get critical mass for a Slack-alternative it’s important to..." and I would add that it's less, er, critical to reach critical mass when you have at least one-way mirroring of Slack, as Zulip does; that way it's less important that everyone agree to move at once.
indeed and I think when small oss-projects just start their own stream and have their own ‘pace’ (which might be even less than a handful messages a week) it’s fine: for (core) contributors it means that an explanation is always retrievable by future users.
@borkdude it seems that a lot of usergroups succeeded initially on slack - but when the main-channels got more popular it shrunk the history (in terms of days), and slowly the ‘abandoned channel’ kicked in
but did they succeed in other platforms that did have history? if not, maybe the channels weren’t that important to begin with? 😉
casual data point: in my Slack instance at work where we do have history, I rarely search for something. maybe once or twice every quarter.
what I got from contacting localgroups and looking them up on meetup is that they often have a separate Slack-team.
@borkdude for local-groups search might be not that important but seeing that something is going (even when that’s about the last meetup, 3 weeks ago) on is important: an empty channel looks abandoned
I have never yet done the invite thing to add one-way mirroring of a Slack channel on Zulip. What is the incantation again?
> casual data point: in my Slack instance at work where we do have history, I rarely search for something. maybe once or twice every quarter. Counterexample: I probably search in my work slack at least once a day. Maybe your memory is better than mine, or your team does a better job of translating slack discussions into other forms of documentation, but I tend to forget the details of conversations that happened months ago, and find it really useful to search back. Of course any searchable-history forum would be equally good for that; not talking it up as a point in favor of slack in particular.
We don’t do many discussions on Slack. We usually do those in a Zoom meeting using screen sharing and then document the decisions in a GH issue
Both of my last two teams we've done a lot of our discussion in slack, which I like exactly because of the searchable history (as well as, in public channels, providing transparency to other interested parties in the organization, which means less time spent having to communicate that stuff outward).
I can't even run zoom 🙂 I got it working for a while in debug mode, and then couldn't update, then that RCE exploit came out & I won't touch it.
Zoom / Hangouts / whatever. I have two colleagues running on Linux who were able to use it btw 🙂
We do use Zoom fairly regularly (works for me on Linux also, although exploit ick), but most of the day-to-day decisions on the ground are made in slack. One other thing I like about that approach is that it's asynchronous-ish; I don't have to interrupt for a scheduled meeting as often. YMMV of course, just saying it's worked well for me.
it works on linux under certain systems, it won't work if you're not using systemd.
Yes, works fine on Ubuntu (Zoom is mandatory with our distributed workforce), and on Android of course.
i think zoom used to have issues with wayland (like fedora) but the last time i used it it worked flawlessly
semi-offtopic clojure question: what is everyone's preferred code line length limits? 79-80, like Python? 100 like Google Common Lisp conventions? 88, like Python black formatter? or none?
80, so I can fit more windows side by side 🙂 (I don't mind going over now & then when it's clearer, but I aim to hit 80 on ~95% of lines)
130, it's the rounding of github's limit (it shows 127 characters before horizontal scrolling is triggered)