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

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