crab
rfc-leadership-council
| crab | rfc-leadership-council | |
|---|---|---|
| 37 | 2 | |
| 5,064 | 6 | |
| 0.0% | - | |
| 9.9 | 2.7 | |
| 4 months ago | 11 months ago | |
| Rust | Markdown | |
| GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
crab
- The Crab Programming Language
-
If you love it so much, why don’t you move there?
Will this be forked, too?
- Rust language forked by community into Crab
-
Rust has been forked to the Crab Language
Even more context: https://github.com/crablang/crab/issues/14
- Sad Crab
-
On the RustConf Keynote
I think https://github.com/crablang/crab is the healthy path forward.
- Rust: The wrong people are resigning
rfc-leadership-council
-
Rust has been forked to the Crab Language
This fork promises "All of the memory-safe features you love, now with 100% less bureaucracy!" Compelling, until you realise that all the commits are auto-merges of rust-lang/rust's main branch. Which means the same teams doing the same work, under a different name.
Rust is experiencing growing pains because they're still figuring out a governance structure that works for everyone. They want to simultaneously keep the current structure of bottom up development where each team (compiler, lang, crates.io, cargo) has the autonomy to make decisions for themselves, but the project as a whole can speak can come to a consensus and speak with a single voice. That's what this RFC tries to capture (https://github.com/rust-lang/rfc-leadership-council/blob/mai...). But the project isn't there yet, and is making these frustrating missteps in the interim. The lack of transparency into these missteps manifests as "bureaucracy" to outsiders like us.
If Crab lang actually attracted people doing the real work of development, they would have the exact same "bureaucracy" as teams tried to figure out how to build consensus and speak with one voice. The fact that they don't have bureaucracy is a direct consequence of them not doing any work right now. None of the people involved in regular Rust work, as far as I can tell, so they might not be aware of this.
Lastly, I want to note that the top comment in this thread is blaming the Foundation, which is simply bizarre. The Foundation very explicitly tries to stay hands off on technical decisions and does not interfere in how the teams organise themselves. You may disagree with that, but it's an inaccurate characterisation.
-
Hey Rustaceans! Got a question? Ask here (15/2023)!
Read eg. https://github.com/rust-lang/rfc-leadership-council/blob/main/text/3392-leadership-council.md as start
What are some alternatives?
rust-typed-builder - Compile-time type-checked builder derive
mimalloc_rust - A Rust wrapper over Microsoft's MiMalloc memory allocator
rustacean.net - Source for rustacean.net, home page of Ferris the Crab.
hashes - Collection of cryptographic hash functions written in pure Rust
rust-artwork - Official artwork for the Rust project.
rumqtt - The MQTT ecosystem in rust
ZealOS - The Zeal Operating System is a modernized fork of the 64-bit Temple Operating System, TempleOS.
rust-playground - The Rust Playground
Home - This is the landing repository for the .NET foundation efforts. Start here!
crates.io - The Rust package registry
bodywork - ML pipeline orchestration and model deployments on Kubernetes.
api-guidelines - Rust API guidelines