This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-25
Channels
- # admin-announcements (2)
- # beginners (36)
- # boot (37)
- # cider (65)
- # cljsrn (92)
- # clojars (3)
- # clojure (225)
- # clojure-austin (5)
- # clojure-belgium (2)
- # clojure-brasil (3)
- # clojure-china (1)
- # clojure-greece (2)
- # clojure-mexico (3)
- # clojure-news (2)
- # clojure-quebec (1)
- # clojure-russia (14)
- # clojure-spec (24)
- # clojure-uk (53)
- # clojurescript (34)
- # cursive (14)
- # datascript (9)
- # datomic (4)
- # defnpodcast (8)
- # devcards (30)
- # dirac (7)
- # editors (7)
- # emacs (1)
- # figwheel (1)
- # hoplon (85)
- # immutant (2)
- # incanter (1)
- # luminus (5)
- # off-topic (41)
- # om (18)
- # onyx (11)
- # perun (2)
- # re-frame (11)
- # reagent (9)
- # ring (3)
- # spacemacs (2)
- # spirituality-ethics (1)
- # test-check (19)
- # testing (12)
- # untangled (14)
- # yada (9)
@akiva: You might want to check out #C0CB40N8K http://whatthefuck.computer/blog/2015/11/01/on-the-balkinization-of-my-chat-communities/ is a better article on the troubles of IRC I think
When working with text, should a \r
generate a newline by itself? Should "foo\rbar"
print on two lines or one? Undoubtedly "foo\nbar"
and "foo\r\nbar"
should span two lines, but fundamentally is the behavior or \r
a DWIM thing or should it be ignored without a following newline char?
@dominicm, oh I’m very well aware of IRC’s problems. I’m not advocating a return to it; I’m quite content with Slack.
We're reaching the illing point of slack I believe. The point where we get kicked off like Reactiflux did
Seriously, though, I'm wondering why Slack's become so popular for open-source dev communities despite its limitations.
searchability, persistence, simple interface, basic code highlighting all out of the box
The problem is that Slack's free version has a 10k message log limit, and the pricing scheme that Slack uses for its non-free version is not designed with large communities in mind.
So searchability and persistence are completely null and void because 10k messages are quickly reached, and as I said, private messages are actually included in this. Some of my private convos are gone because of the message limit.
Plus, as the article dominicm linked, they're prone to shutting down large Slack communities that aren't paying the bills because they're using the free plan.
persistence is most useful when you jump in and want to see what someone said a few lines ago
Also, basic code highlighting isn't much of a feature, Discord's got it too. Any Electron-based messaging app doesn't need to jump through hoops to get syntax highlighting, it's as simple as making use of one of the plentiful JS syntax highlighting libs.
Arguably, Discord's better than Slack. Searchability can be achieved through a bot that logs messages - Discord has a stable bot API now - and it supports pretty much every single thing Slack does. The only downside is that the channel system isn't really suited for us, as the Clojure community prefers to have on-topic channels for every single thing instead of bigger channels serving multiple purposes. I think that's the hitch.
On a Discord server, you are joined to every single channel you can access, with no way to opt out.
There's also pinned messages and a mentions viewer. There's not a small possibility that the Discord devs will add an integrated search feature at some point that searches some amount of history. Wouldn't be as good as Slack's, still, though.
It's been discussed many times, in here and #C0CB40N8K (and many things besides, the whole community aspect of building a clojure community together, in clojure - how meta)When I founded Clojurians slack was the best tool for the Job, we have been slowly outgrowing it since then. However moving a nearly 7,000 strong community is no small feat