That's excellent news. Being locked out of the community by virtue of it being hosted on a proprietary service, requiring a proprietary code blob to access, was one of the biggest sour notes I had coming to Julia.
(Now if only discourse.julialang.org links would render without Javascript!)
I don't quite get this concern about proprietary JS. I agree JS can be malicious, but it has nothing to do with license. Or you can say you don't want to give your data to Slack.
I sympathize with those who object to proprietary JS, but in my case I'm mostly annoyed at having to run code just to read static content - quite heavy code, too. When I have a lot of discourse.julialang.org pages open, my browser noticeably chugs.
Often it has nothing to do with maliciousness or data aggregation, it's a matter of principle: not supporting proprietary software.
Re:Zulip 3.0: Threaded Open Source Team Chat
by oehtXRwMkIs on Thursday July 16, 2020 @04:22PM
(#23863409)
Remind me of Rust with the added bonus of requiring a GitHub account to upload crates.
Re:Zulip 3.0: Threaded Open Source Team Chat
by dijit on Thursday July 16, 2020 @05:17PM
(#23863917)
FWIW Rust has a zulip, I'm on it, it's the only community I'm part of on zulip.
It's mostly frequented by the infrastructure teams. :)
Apparently the compiler team is also >primarily< there: https://rust-lang.github.io/compiler-team/about/chat-platfor...
Re:Zulip 3.0: Threaded Open Source Team Chat
by PudgePacket on Friday July 17, 2020 @03:01AM
(#23867918)
You can add crates from other registries or git urls.
https://doc.rust-lang.org/cargo/reference/specifying-depende...
That's not the issue - the issue is uploading crates to crates.io not using crates published by others.
Re:Zulip 3.0: Threaded Open Source Team Chat
by PudgePacket on Friday July 17, 2020 @12:20PM
(#23872176)
That's what I meant though. Neither parts needs to use crates.io.
Re:Zulip 3.0: Threaded Open Source Team Chat
by oehtXRwMkIs on Sunday July 19, 2020 @03:10AM
(#23887596)
The issue is that crates.io is essentially a GitHub account owners only club. Although I guess that's Rust development in general.
Nice, I wandered on to the Zulip Chatroom for Quarkus. It didn’t take me very long to figure out the interface: it was very intuitive, and I absolutely LOVE the syntax highlighting support AND topic centered conversations! For technical conversations when you gotta share a lot of code, it makes a HUGE difference when you can share code snippets that are easy to read. Slack allows this with the upload a snippet feature but it’s hard to use and the UX of snippets is kinda atrocious.
If I were to start a new community, I would absolutely go with Zulip.
Re:Zulip 3.0: Threaded Open Source Team Chat
by maneesh on Friday July 17, 2020 @01:23AM
(#23867326)
Is there any sort of 1:1 syncing integration between slack and zulip? It would be awesome if posts in public channels would show up on either app, regardless which was posted -- would make transition easier for teams!
And -- if there isn't, if any developer is interested in working on it, I'd possibly be willing to pay -- and we could probably release it as open source! [email protected]
You can use Matterbridge for that. See https://github.com/42wim/matterbridge/wiki/Section-Zulip-(ba... and https://github.com/42wim/matterbridge/wiki/Section-Slack-%28....
The topics model is fantastic, having proper markdown and LaTeX support is also killer.
The development team for Zulip is also really responsive and friendly. Coming from Slack, it was a breath of fresh air to be able to make an issue on their GitHub issue tracker and have fast, friendly thoughtful replies and quick action.
[1] https://julialang.zulipchat.com/#recent_topics if you wanna check it out