Hacker News Reader

Comment by dTal | Hacker News Reader

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!)

View on HN

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.

Often it has nothing to do with maliciousness or data aggregation, it's a matter of principle: not supporting proprietary software.

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.

Remind me of Rust with the added bonus of requiring a GitHub account to upload crates.

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...

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.

That's what I meant though. Neither parts needs to use crates.io.

The issue is that crates.io is essentially a GitHub account owners only club. Although I guess that's Rust development in general.

Reply on news.ycombinator.com