Increasing Rust's Reach 2018

Applications for our 2nd Increasing Rust's Reach Program are OPEN! :sparkles:

Check out more in the blog post:

or go straight to the website:

feel free to ask questions here or message :smile:


Hey @ag_dubs! Great initiative.
What is the level of rust language experience expected from the applicants!
Are beginner applicants welcome ?

Same question as @cg-cnu I am learning Rust, and I am following the book second edition. I have just finished the Chapter 8 HashMaps. Once I finish the book I would like to participate in a Rust project.

yup! this program is designed to work well for people of all levels, from advanced to total beginner. you should have experience programming in SOME language, but any language works, and it's ok if you are still a beginner :slight_smile:

that's a great level to get involved. we've had participants who only start reading the rust book after they are accepted. the only real requirement is that you want to learn rust and have previous experience in some programming language.

1 Like

That's great to hear! Thanks to the rust community for being so inclusive! :love_you_gesture:

Hi @ag_dubs! This seems like an awesome opportunity. Do you think it would be possible to be part of the program if I'm already doing a full-time internship during the program's duration?

I personally don't have a problem with committing nights or after work hours for the program, but I'm sure that could be an issue with the Partners. Thanks!

I would encourage you to apply but to perhaps note that, just in case! The Partners can be very flexible, but that flexibility is slightly different for each one, so it would be good context when reviewing your app :slight_smile:

1 Like

Sounds good, thanks!

I think the most important thing the Rust project can do to increase the use of the language is to make it easier to learn. And I think the way to do that is to provide a document that teaches how to use Rust in a way that avoids the difficult corners of the language that can be stumbled upon if you don't know what you are doing, but are avoidable.

This is a bit like user-interface design -- good UIs give you access to every aspect of the capability/service behind them, but the most oft-used, most important aspects of the service are front and center.

I don't think the Rust Book accomplishes this, nor does Jim Blandy's book (which I think is excellent in many ways). Both document a wide swath of the language, but don't home in on a methodology that allows you to avoid lifetime hell or borrow-checker hell unnecessarily. I think experienced Rust programmers know how to do this and beginners don't. I'm suggesting a document that captures what they've learned that allows them to co-exist with the Rust compiler and avail themselves of the advance that Rust represents over C and C++ without encountering avoidable problems.

1 Like

I'm really excited about this initiative for two reasons:

  • reduces the latent exclusion that the status quo offers :tada:
  • demonstrates to other open source communities that they can be better :loudspeaker:

Thanks very much to @ag_dubs, @carols10cents, @avadacatavra and @aidanhs for taking the time to get this off the ground :slight_smile:

Don't want to derail this thread.. but have you considered my book (Rust in Action)? Its chapter on lifelines (have linked to the "liveBook" HTML version) presents three approaches to sidestepping the borrow checker while you're learning the language. I am be very interested to hear if this is closer to what you're after :slight_smile:



I think it is better to post this in a seperate thread. There is a magic button somewhere here that does that.