Nicholas Matsakis - Rust 2024 and beyond

This year will be the 3rd Rust edition, Rust 2024, and marks 9 years since Rust 1.0 was released in May of 2015. In that time Rust has become a foundational technology used everywhere from kernels to spacecraft to cloud data centers. As Rust (and its community) grows, how do we stay true to our mission of empowering people to build everyone to build reliable and efficient software? In this talk we'll look at what has been happening lately with Rust as well as some of the challenges that we will need to tackle over the next few years.

[@Speykious]

Kinda crazy to me to see cve-rs mentioned lol

[@sirgibsonable]

Dude--that was awesome work!

[@xshady2967]

love it xd

[@rodelias9378]

Great talk Niko. Rust is getting better each day!

[@haloboy777]

This talk made me more invested in rust after 3 years of partial use. Would love to use it full time.

[@josefvacek6472]

what is the breathing in the background lol

[@culturedgator]

Finn getting madder at the Async/Await

[@pramodjingade6581]

Async sleep() 😂

[@stokotov2140]

L.. .m😊

[@NeotenicApe]

i hate that amazon has infiltrated rust

[@1____-____1]

Why? No different than RHEL paying Kernel devs to do stuff.

[@artemartem5336]

Hey rust guys, please make "await future", not "future.await"

[@Mankepanke]

It's much better to have it to the right though? (await (await foo).bar)?.baz vs foo.await.bar.await?.baz

[@artemartem5336]

@@Mankepanke let bar = await foo(); let baz = await bar();

[@maximus1172]

this is not javascript, this is rust

[@ovi1326]

​​@@artemartem5336naming intermediate values is hard and this one doesn't work well with results and options. like you'd still have to write ``` let x = (await make_x())?; ``` instead of ``` let x = make_x().await?; ```

[@artemartem5336]

@@ovi1326 Man, how to understand this semantically ? make_x().await - is it extension of make_x() result? Is result of make_x() = future? What is future.await ? Field of Future trait?