41
What we heard about Rust's challenges, and how we can address them | Rust Blog
(blog.rust-lang.org)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 20 Mar 2026
41 points (91.8% liked)
Rust
7884 readers
29 users here now
Welcome to the Rust community! This is a place to discuss about the Rust programming language.
Wormhole
Credits
- The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)
founded 2 years ago
MODERATORS
My biggest issues with rust are
It's good to know I'm not alone. But I'll never choose C/C++ over Rust. If I need speed and typing, it's Rust, no questions asked. For everything else, there's Python. I just wish Rust has better GUI frameworks...
Domain are also susceptible to being hijacked, unfortunately.
Also what do you mean by github only?
Domains are, sure but the space is much much larger. With namespaces the space is for example
namespace x crateinstead of justcrate. With domains it's impossibly large. And if you introduce some kind verification with domains e.g putting something in the DNS TEXT entry, or calling a well-known path, or or or, you basically can't squat anything well-known anymore.As for github, you must have a github account to create a crate on crates.io. to my knowledge there is no alternative crates registry. Point me to one if you do, because I'd be grateful and willing to publish my crates there.
@onlinepersona @Miaou for github they said for years that they would welcome patches but so far nobody came, nor payed someone to do it for them.
I find it ridiculous that they started with github in the first place, but who am I to judge. It is ironic that in order to contribute a non-github solution, you still need to create a github account to make a PR.
@onlinepersona I'm quite certain that if you have a working solution, visible somewhere on internet, you can ping them on zulip/discourse to ask someone to pull your code.
Oh really? 🤔 Every project on Github that I've tried to contribute to from outside has been resistant to it. But maybe I could give cargo.io a try. Zulip you say? Interesting choice... requires creating yet another account since it doesn't seem to be federated...
@onlinepersona Given that this subject was already brought up, and regular people from the project said that their is interest for removing the dependency to github (but not leave it, Microsoft is one of the top contributor), I assume that some people would be willing to help the integration a working prototype.
In case you need it:
https://rust-lang.zulipchat.com/
Your second point has been a focus area for them for years, and we've seen it improve with async fn in trait, async closures, etc. Hopefully we see that continue to improve over time.
The third point has a solution in the works already (at least for crates.io). The accepted (I believe) proposal is that crates themselves act as "namespaces" and you can publish crates like
bevy::renderorhyper::utilsthat get loaded under some parent module by the compiler. Publishing crates with names containing::would be constrained to those who maintain the parent crate (sobevyorhyperin that case).