- rfc-leadership-council VS crab
- rfc-leadership-council VS mimalloc_rust
- rfc-leadership-council VS hashes
- rfc-leadership-council VS rumqtt
- rfc-leadership-council VS rust-playground
- rfc-leadership-council VS crates.io
- rfc-leadership-council VS api-guidelines
- rfc-leadership-council VS hurl
- rfc-leadership-council VS Home
- rfc-leadership-council VS cargo-auditable
Rfc-leadership-council Alternatives
Similar projects and alternatives to rfc-leadership-council
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
crab
A community fork of a language named after a plant fungus. All of the memory-safe features you love, now with 100% less bureaucracy!
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
Home
This is the landing repository for the .NET foundation efforts. Start here! (by dotnet-foundation)
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
rfc-leadership-council reviews and mentions
-
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
Stats
rust-lang/rfc-leadership-council is an open source project licensed under Apache License 2.0 which is an OSI approved license.
The primary programming language of rfc-leadership-council is Markdown.
Popular Comparisons
Sponsored