How Rust Views Tradeoffs 

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

I'm going to name my child Rust

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

The discussion on using what tools align with your values at 23:57 - 25:12 perfectly illustrated why I love Kotlin and Rust, and why I hate working with Javascript so much, where others love it. JS is just...antithetical to everything I hold dear.

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. Mostly we carry out that maximization by making interactions between people based on mutual consent: if you want to interact with me in a way I think I won't like I can say no, take my ball and go home; you can do the same to me. If we both say yes, that must mean we both believe we'll benefit from the interaction-that is, we believe it's win-win. There are corner case exceptions to this rule, but they are just that: exceptional corner cases. The fundamental idea in economics is that win-win is possible and good, and there's a system for achieving that which is fairly simple (although the fully detailed argument is a lot less simple than my sketch of the main point).

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.

Bending the curve lol

cargo relies on the internet to function. Supporting old hardware is going to be next to impossible anyways. ... which is especially painful for FreeDOS development ... which has 2's complement notation

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. Seriously.

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.

Engaging speaker.

Well done! Great presentation. Also I'm pretty sure why you are "between" jobs... Maybe self employment is the best option for you!

This guy: "guys value different things then me, and prefer different languages, and that's cool" Other rust core devs: "The government should forcefully regulate the use for rust in applications!"

I like his presentations but 10:00 - none of them are inherently against each other. I see no reason to single out throughput/latency. How choices are against each other depends on how bounds are defined - those may be rather fuzzy sometimes. If you inline everyting - binary gets larger - you get more cache misses, so "everything gets faster" is not also always true.

🤟🤠

Absolutely amazing! Thank you!

Performant is a word in French.

dark mozilla give us the erlang-like pre 1.0 rust

Talk starts at 15:26

the rust video starts after 16:00 only, SAVE your precious time

Awesome talk, thank you!

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

Wow. Nice talk.