Episode Details

This Week in Rust - Issue 444

Published 3 years, 8 months ago

Description

Highlights from This Week in Rust - Issue 444. This week features a juicy post-mortem, open source, open hardware, and lots of news from around the Rust ecosystem.

Contributing to Rustacean Station

Rustacean Station is a community project; get in touch with us if you’d like to suggest an idea for an episode or offer your services as a host or audio editor!

Timestamps & referenced resources

[@00:00] Welcome

[@00:10] - Introduction
[@00:50] - Agenda
[@01:23] - Quote of the week

This is the difference in approaches of the two languages. In C++ if the code is vulnerable, the blame is on the programmer. In Rust if the code is vulnerable, Rust considers it a failure of the language, and takes responsibility to stop even “bad” programmers from writing vulnerable code. I can’t stress enough how awesome it is that I can be a careless fool, and still write perfectly robust highly multi-threaded code that never crashes.
- [@03:09] Allen: Rust is both good and bad at marketing
[@03:30] - Crate of the week
- [@04:15] - Tim and Sean discuss parsing in episode 2022-05-26 at 47:10

[@05:10] Official Notices

[@05:22] - Announcing Rust 1.61.0
- Custom exit codes from main
  - [Note from Tim: I say “termination crate”, but should have said “Termination trait”.]
- More capabilities for const fn
  - “Basic” handling of fn pointers
  - Add trait bounds to a const fn
  - dyn trait and impl Trait support
- Stdio handles can be locked directly
- Several stabilized APIs

[@08:07] Highlights

[@08:27] - Developer survey: JavaScript and Python reign, but Rust is rising
- [@09:09] - Sean: “Rust adoption has nearly quadrupled in the last two years, going from 600k developers in Q1 2022 to 2.2m in Q1 2022.”
[@13:00] - Redust by Will Nelson
- [@13:50] Allen: I think the comments are actually more interesting. They are starting to point to something really—I don’t know whether it’s good or bad for the community—where, you know, peopl