The entire moderation team resigns, effective immediately. This resignation is done in protest of the Core Team placing themselves unaccountable to anyone but themselves.
As a result of such structural unaccountability, we have been unable to enforce the Rust Code of Conduct to the standards the community expects of us and to the standards we hold ourselves to. To leave under these circumstances deeply pains us, and we apologize to all of those that we have let down. In recognition that we are out of options from the perspective of Rust Governance, we feel as though we have no course remaining to us but to step down and make this statement.
In so doing, we would offer a few suggestions to the community writ large:
- We suggest that Rust Team Members come to a consensus on a process for oversight over the Core Team. Currently, they are answerable only to themselves, which is a property unique to them in contrast to all other Rust teams.
- In the interest of not perpetuating unaccountability, we recommend that the replacement for the Mod Team be made by Rust Team Members not on the Core Team.
- We suggest that the future Mod Team, with advice from Rust Team Members, proactively decide how best to handle and discover unhealthy conflict among Rust Team Members. We suggest that the Mod Team work with the Foundation in obtaining resources for professional mediation.
- Additionally, while not related to this issue, based on our experience in moderation over the years, we suggest that the future Mod Team take special care to keep the team of a healthy size and diversity, to the extent possible. It is a thankless task, and we did not do our best to recruit new members.
In this message, we have avoided airing specific grievances beyond unaccountability. We've chosen to maintain discretion and confidentiality. We recommend that the broader Rust community and the future Mod Team exercise extreme skepticism of any statements by the Core Team (or members thereof) claiming to illuminate the situation.
We are open to being contacted by Rust Team Members for advice or clarification.
Sincerely,
The Rust Moderation Team (Andre, Andrew and Matthieu)
:desolate:
Looks like you guys are all regretting loading up all your eggs in rust instead of crystal lang.
This message brought to you by Crystal Gang ©
I write all my code in a basic Turing machine. Become ungovernable.
Just a notebook and Russell-era Lambda calculus for me.
imagine using a language with predefined special syntax instead of simply creating your own
this post made by Common Lisp Gang
Knowing nothing about either, what makes crystal better than rust?
Crystal lang is like Rust without a borrow checker, and more importantly, without semicolons. The syntax is like Ruby, but performs fast like golang. It's compiled with a garbage collector like golang, but also it's kind of like "what if golang was good?". Unlike ruby, the macros are compile time instead of runtime, also unlike Ruby, the type system is closer to rusts.
It sounds neat, but it doesn’t seem like a direct alternative to rust. For me, the core feature of rust is the borrow checker and the ownership system, which give you most of the convenience and safety of garbage collection but without any runtime overhead.
Of course I don't suggest Crystal for embedded work or non-scripting parts of game engines, but we're on a website written in rust. All the borrow checker does for lemmy is exclude 99% of your backend devs from contributing.
A back end written in Crystal would have the same issue but worse. It is far less popular, see e.g. Invidious and how little that has progressed after the lead maintainer quit last year despite being a far more popular project than Lemmy