How Rust Views Tradeoffs

Video with transcript included: bit.ly/2Y4DfNy
Stephen Klabnik takes a look at some tradeoffs in the design of Rust, and how that makes it more suitable for some kinds of projects than others. In particular, he talks about Rust's "bend the curve" philosophy towards tradeoffs.
This presentation was recorded at QCon London 2019: bit.ly/2VfRldq
The next QCon is Qcon San Francisco 2019 - Nov 11-13, 2019: bit.ly/2ZFJW9S
For more awesome presentations on innovator and early adopter, topics check InfoQ’s selection of talks from conferences worldwide bit.ly/2tm9loz

[@JustAnotherJakeyG]

I've seen like 3 vids of this guy in the last day and I've seen his hair go through its own anime training arc

[@JimPekarek]

The discussion on using what tools align with your values at

[@rudiwinkelstein2483]

I'm going to name my child Rust

[@jonaskoelker]

Around the 10ish minute mark Stephen talk about win-win vs. zero-sum interactions. One of the key teachings of economics is that the world is full of win-win opportunities, and we collectively do ourselves a favor by maximizing our utilization of those opportunities.

[@halneufmille]

I'm an enthusiastic Julia user but I got to say having a documentation committee would go a very long way for us. Quality and exhaustive doc is almost as important as quality packages for language adoption. Right now, it still feels we're in the "let a thousand flower bloom" phase without many style criteria and asking new users help improve the doc while learning.

[@marlls1989]

I came from Haskell, and I am loving the Rust type system... it is just what was missing on C

[@first-thoughtgiver-of-will2456]

Rust has one of the best documentations I've seen since I learned Java (to me its better than that and more organized as well) thanks if you had a part in that.

[@ailuros_]

Absolutely amazing! Thank you!

[@JockeTF]

Awesome talk, thank you!

[@birkett83]

Throughput vs latency can be a fundamental tradeoff in the specific context of choosing packet sizes. With a fixed link speed larger packets allow more throughput because the ratio of payload to header is increased, but it aldo takes longer to transmit a complete packet. This came up in the design of the ATM protocol which was widely used for telephone and data networks in the 1980s and 1990s. The US wanted 64-byte payloads, but France wanted 32 bytes because this would have kept the latency low enough for them to build an ATM voice network across the whole of France without using echo-cancellation. They compromised and made everyone unhappy with 48-byte frames. with 5 bytes of header, making 53 bytes total.

[@dorobokino]

I love how elucidating this talk is, I really like his style of communication mixed in with humor

[@robbietorkelsonn8509]

cargo relies on the internet to function. Supporting old hardware is going to be next to impossible anyways.

[@TroyNeubauer]

Bending the curve lol

[@TremereTT]

Well done! Great presentation.

[@adinesh7989]

Wow. Nice talk.

[@sergesolkatt]

🤟🤠

[@PetrGladkikh]

I like his presentations but

[@stephenjames2951]

Engaging speaker.

[@ThePandaGuitar]

Performant is a word in French.

[@anumangrocers6577]

Talk starts at