5 ms·
No blame/shame taken! Everyone has their own opinions as to the work to be done. We now have a yearly roadmap process for each year, and are soon going to be o
by steveklabnik 9y ago
No blame/shame taken!
Everyone has their own opinions as to the work to be done. We now have a yearly roadmap process for each year, and are soon going to be opening that up to community discussion. Feedback from everyone that cares about Rust is extremely important!
That's also part of why I didn't elaborate; my thoughts on that are a whole big post unto itself. That said, my personal focus is on documentation, ease of use, and growth, so those are some broad areas in which I'd like to push hard on next year. The funny thing about goals is that they often tie into other goals, for example, I believe that documentation is a huge part of ease of use. Same with how other people's goals might fit into my goals; language design is also a big part of ease of use, for example.
What I will say is that I'm currently prototyping a complete re-think of how Rust does documentation; I'm excited to share it but it's not ready yet.
To briefly comment on some of the points you've raised:
> I don't consider it important to be able to compile Rust to JavaScript
We share this opinion, but compiling to WebAssembly is a whole different ballgame.
> There are scenarios where rustup and cargo are not acceptable. Is this on the radar?
It's hard to say without knowing more details of what exactly you mean; distros are already packaging Rust and libraries, for example. In general though, this is a thing we've put a ton of effort to in the past, and I expect to have even more in the future.
> Rusts only Tier 1 platforms are of the the backdoored x86-family
A few things; we've been thinking about reconsidering the tier system because it isn't a good representation of support. ARM is basically tier 1 but there's a tiny detail about it that prevents us from fitting it into today's "tier 1" rules.
What we need to improve platform support is experts in those platforms to help us. With our current people, we're doing what we can, but we'd love for people to get involved and drive better support for more platforms.
This stuff absolutely matters; consider Firefox, for example: they have Tier 1 platforms that aren't Tier 1 for us (ARM), but they do depend on us. That's a problem!
> independent implementations
There's one significant independent implementation, but in some sense, this is something we can't actually do ourselves, otherwise it wouldn't be independent. :) I personally don't think this is a massive problem for Rust today; eventually it would be nice though. It does factor into how we do some things, as we try to pretend as though we have alternative implementations, even though we really don't today, in preparation for that future.
- madez 9y agoThanks for your elaborate comment. It is interesting to read and insightful. I just have comments for select sections: >> I don't consider it important to be able to compile Rust to JavaScript > We share this opinion, but compiling to WebAssembly is a whole different ballgame. If I understand correctly, WebAssembly is essentially the same as JavaScript, and therefore something I'd like to avoid. I do not want random executable code from websites, that my browser then automatically executes. I don't think sandboxing is a solution, because it's an inherently impossible problem. Externally controlled and unaccaunted executable code is _always_ bad. Instead, let's fix some restricted non-turing complete markup language, like HTML, and stay with that. It's an optimal solution. Maybe, probably, I'm missing something here, but JavaScript and WebAssembly seem to be things that are not in the interest of users. >> There are scenarios where rustup and cargo are not acceptable. Is this on the radar? > It's hard to say without knowing more details of what exactly you mean; distros are already packaging Rust and libraries, for example. In general though, this is a thing we've put a ton of effort to in the past, and I expect to have even more in the future. Cargo and Rustup seem to be in competition to the existing package management systems. Why not integrate rust and the libraries into the existing packagement systems, like so many other software projects do? How is Cargo and rustup better than Apt? Also, Apt is perfectly usable without internet. One can download the entire Debian archive to a hard drive and use it without any external connections. How would I do that with Cargo and Rustup? This is just one point. There are so many scenarios Apt already has solutions for, that Cargo and Rustup probably didn't even consider yet. Anyhow, clearly this issue is noted and even already worked on. That's more I could ask for. Another thing I forgot to mention is IDE support. I read that Rust is now supposedly supported in Gnome Builder, but I see no option to create a Rust project. This is not the responsibility of the Rust team, and it's just an anecdote, but it affects Rust and it's usage and growth.
- steveklabnik 9y agoYou're welcome! And thanks for your posts too. > WebAssembly is essentially the same as JavaScript In some senses, but not others. Regardless of personal feelings though, WebAssembly isn't just happening, it's already happened. And also regardless of personal feelings, many people in the Rust world seem to be very excited about WebAssembly; see https://mgattozzi.com/rust-wasm https://mgattozzi.com/rust-wasm for example. (I personally am very interested, but if the community was against it, would accept that. It seems like the majority, at this time, is pretty pro.) > How is Cargo and rustup better than Apt? There's a multitude of ways to tackle this problem, but I'll give you the biggest one: I'm a Windows user these days. Apt is 100% useless to me. This problem is the same even on Linuxes, while I do use Debian, I used to use Arch: Apt would be 100% useless to me. > Apt is perfectly usable without internet. Cargo is perfectly usable without internet. It's a hard requirement of projects like Firefox, and the various distros that are shipping Rust today. Now, we want to make it even easier to use without internet, so there's work to be done, but the fundamentals already exist and are used in production systems today. > Another thing I forgot to mention is IDE support. Yeah, this is super huge, agreed. We've been working on various things, but obviously it depends on what IDE you use, and there's a long tail there. We'll get there!