4 ms·

I am surprised that it is written in Rust. Bi-directional long live connections don't require Rust's raw horsepower. Maybe it's needed for audio/video streaming

by didip 2y ago

I am surprised that it is written in Rust. Bi-directional long live connections don't require Rust's raw horsepower. Maybe it's needed for audio/video streaming? Is the API discord compatible? That's basically necessary for adoption.

vivzkestrel 2y ago
what do you think it should be written in? golang?
- didip 2y ago
  Golang would have encouraged a lot more contributions, e.g. https://github.com/mattermost/mattermost https://github.com/mattermost/mattermost (I am not affiliated with them).
  - ZeWaka 2y ago
    I don't think that correlation of number of commits implies causation.
airstrike 2y ago
I would pick Rust for 9/10 of problems today.
kibwen 2y ago
> Bi-directional long live connections don't require Rust's raw horsepower. If you're an app dev who's really and truly serious about lowering the barrier to self-hosted services, then you need to consider what the install and deployment step looks like. For languages like Rust that default to producing a single static binary, that's as easy as it gets. Likewise, you need to consider that users might want to self-host on a potato, which is where Rust's efficiency shines even for small services. These are both things that Mastodon got horribly wrong, for example, by choosing to use Ruby.