code::dive 2017 - Alex Crichton - Concurrency in Rust

[@samyaks]

Great talk! Especially useful for a beginner like me, shows all the different kinds of concurrency and parallelism that Rust supports.

Does he say "so, alright" or "sorry" after he's done with each explanation? ^^ Anyhow, great talk! Thanks!

[@anataro210]

"double every 6 months" into the trash it goes

[@louiscloete3307]

Well, core counts do double every 1-2 years today, so the stuff that doubles changed, but engineers are still trying to squeeze more out of the hardware.

[@yiandev4368]

stop evangelizing the language sooo much, talk about rust's problems and challenges and how to aproach them, im sick of rusts religious talks for the last 2 years, its time to move to the next level

[@TaiDesHen]

care to list these problems you are talking about?

> talk about rust's problems and challenges and how to aproach them like how traditional callback-based futures turned out to be a poor choice for Rust, so they came up with poll-based futures instead?

[@cst256]

So he's supposed to go to a conf and tell people why they should not use Rust? It's not even a mainstream language so obviously people know it's pitfalls otherwise they would have been using it instead of C++/Go already.

[@MajorBreakfast]

TaiDesHen He listed two reasons why futures all poll based: Overhead due to additional heap allocations and necessity for all involved types to be Send or Sync (which is frequently impossible). Downsides of Rust: Embedded development isn’t mature yet (cannot be done with stable rust, avr support even requires a fork of rust), untrodden territory in many fields (e.g in cpp there are math libraries that were able to mature over many years), incremental compilation only landed in February 2018 with version 1.24 and more optimizations are still on its way, and finally the lifetime rules are often stricter than they should be (non-lexical lifetimes are coming though). But if you ask me, Rust will soon get even better. IMO it is already easier to work with than cpp because cmake and no package manager are a real pain. Many big projects even use python for build scripts (e.g. for code generation in math libs) because cpp is just too hard to work with (rust build scripts are usually written in rust and build automatically before the rest of the package). Plus there are of course all the reason Alex mentioned in his talk. I see a bright future for Rust.

[@ThePandaGuitar]

It’s always needed to get more developers to help and improve the language.