News for hackers. Stuff that matters.
Re:Rust concurrency: the archetype of a message-passing bug by ashtonkem on Monday June 22, 2020 @10:33AM (#23600608)
My experience is that Rust advocates often go well out of their way to specify the limits of Rust’s protection, and will even rush in to correct someone who over promises what Rust can give you.
Re:Rust concurrency: the archetype of a message-passing bug by htfy96 on Monday June 22, 2020 @11:00AM (#23600964)
r/rust and users.rust-lang.org are informative and sensible when it comes to limitations. Twitter and, well, random programming discords are often full of cults
Re:Rust concurrency: the archetype of a message-passing bug by lostcolony on Monday June 22, 2020 @01:31PM (#23603030)
Yeah, I've never criticized Rust advocates for not talking enough about Rust. :P

But seriously, yeah, the seasoned Rustaceans I've known have been pretty thorough in giving downsides/limitations as well. It's something I love about a language; when the voices in it are aggressive in talking about things it does poorly, or use cases it's not optimal (I still love that Erlang's official website has a section for when _not_ to use it).

Re:Rust concurrency: the archetype of a message-passing bug by yencabulator on Tuesday June 23, 2020 @06:19PM (#23621096)
That doesn't sound like "fearless concurrency", though.