This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-11-23
Channels
- # admin-announcements (38)
- # announcements (1)
- # aws (1)
- # beginners (195)
- # boot (1)
- # business (3)
- # cider (100)
- # cljsrn (37)
- # clojure (99)
- # clojure-russia (69)
- # clojure-switzerland (1)
- # clojurescript (120)
- # datavis (26)
- # datomic (23)
- # devcards (4)
- # editors (38)
- # hoplon (18)
- # ldnclj (27)
- # lein-figwheel (28)
- # off-topic (50)
- # om (329)
- # onyx (255)
- # portland-or (1)
- # re-frame (8)
- # reagent (18)
- # spacemacs (5)
- # testing (1)
do people really prefer slack to irc? its a shame so much activity moved here imo
@danielstockton: it has pros and cons. The pro is that there are more people here now than there were ever on IRC.
i suppose, but do we want those people?
just kidding
it's harder to keep up-to-date with everything split over multiple slack channels and irc
but its good that there's more activity overall
Compared to IRC I quite like the fact that Slack has search (or rather, would if it weren't a free account) and you don't loose messages when you're offline.
Plus it's an umbrella site for all the satellite projects like reagent or immutant or whatever.
freenode has lazybot though, which is saving all the logs
so you don't lose messages there either
and i find it much easier to read through those than slack, which is imo a noisy interface
i don't need to see everyones avatar
@danielstockton I totally felt the same way for the first few months after my team convinced me to standardize us on Slack. It's jarring having the excess information (after coming from IRC), for sure. For my team, I enabled the slack IRC gateway and for awhile I used either to communicate with the team. But alas, eventually the web interface won out
@danielstockton: You can enable 'Compact' mode in Preferences
I see Slack winning over IRC long-term for the same reason web applications are winning out over thick clients and installed applications. Convenience and ease of access. Anyone can hit a URL and join a Slack community, and the presentation is overall more friendly to casuals. IRC, though still quite simple to use, I feel is indisputably more difficult than Slack to learn.
@malch: that's definitely an improvement
kevinmershon: agree but most clojure developers aren't casuals
Granted, but it's good to be a welcoming environment to the full spectrum of skills, especially rookies and junior developers who want to learn and improve
Well, maybe most Clojure developers aren't casuals and don't mind IRC, but if by having Slack you can save just one person from starting to learn programming with Java, then it's worth it P ;
kevinmershon: well irc is 25yo, I have seen it declared dead many times, and it's still going very strong
@kevinmershon: also slack is closed/proprietary, could be bought tomorrow by X and change radically (for the worse or better) for instance
@mpenet: By no means am I saying IRC is dead!
And yes, I agree that with Slack's closedness we face an unknowable future as far as its viability for a long term stable community platform.
Iâve been using IRC for about a dozen years, still use it all the time and like it a lot, but itâs very easy to see why some people would prefer Slack
Also, other than Slack being proprietary, I canât really to point to anything that would make me rate IRC higher than Slack
I find IRC less disruptive, plus it has better tooling (for me), and the open protocol is a biggy too
Have you tried Compact mode for Slack? Itâs pretty minimalistic I think, though itâs a shame I canât hide the channel bar
I use irssi as my IRC client, so it doesnât have a permanent channel bar, just the numbers on the bottom when something happens
oh disruptive as in work flow wise, I've accepted ignoring IRC for most of the time and only look when I want to. Slack is like nagging and demanding attention, esp when it is also used for work. I havn't gotten to the point where I can ignore it and not feel bad
I think you can change notification settings etc per team, and I think theyâre working on making Slack work better for public channels / teams. To be honest, using Slack as a public forum like this feels kind of.. hacky
Jeez, every disruption is bad. For notifications the pull principle should be the only allowed on. Push is so bad in that regard.
I think it's absolutely hilarious how we've been discussing Slack's longterm viability and stability for the community, and here it's suffering intermittent downtime today.
This was my favorite Twitter response: "The @SlackHQ engineers right now https://media.giphy.com/media/dbtDDSvWErdf2/giphy.gif "
http://elbenshira.com/blog/the-end-of-dynamic-languages/ <- Dynamic languages are dead, don't want to flame, but for me of course no! đ