GHC and the future of Freenode
carter.schonwald at gmail.com
Thu May 20 01:58:24 UTC 2021
I definitely find Zulip confusing and have failed to use it every time I’ve
If normal threading is lasagna layers, Zulip threading is like trying to
hold cooked spaghetti in your ha d.
On Wed, May 19, 2021 at 2:40 PM Alex Rozenshteyn <rpglover64 at gmail.com>
> (I'm a little ashamed that I lurk on this list but the thing that brings
> me out of lurking is a post on communication technologies)
> Not Zulip.
> Please not Zulip.
> I've used Zulip once many years ago, and once this year. Both times, its
> interface felt clunky, and it felt like it was trying to get the best of
> IRC, Slack, and a BBS and instead getting the worst of all the worlds.
> Synchronous communication was confusing, asynchronous communication was
> limited, and topics and channels didn't really do anything to organize
> I have two alternatives to add to consideration:
> * Mattermost: it's an open-source clone of Slack, which has its advantages
> and disadvantages, but at least it's familiar and heavily used UI
> * Discourse: it's an asynchronous communication tool, but that may
> acceptable or preferable, and there is already a Haskell Discourse set up (
> On Wed, May 19, 2021 at 11:59 AM Ben Gamari <ben at well-typed.com> wrote:
>> Carter Schonwald <carter.schonwald at gmail.com> writes:
>> > I personally vote for irc. Perhaps via Libera.
>> > What are some example vibrant technical communities on matrix? I’ve
>> > experienced such on irc but less so via more recent / newer platforms
>> I know that many subcommunities within the Rust community use Matrix. I
>> have had quite good interactions in this context. Frankly I think that
>> most of these newer options are technically much more conducive to
>> technical collaboration than IRC.
>> - Ben
>> ghc-devs mailing list
>> ghc-devs at haskell.org
> ghc-devs mailing list
> ghc-devs at haskell.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ghc-devs