Oddbean new post about | logout

Notes by 854b15b1 | export

 Update: I was wrong, both WhatsApp (months ago) and Signal (this week?) rolled out the ability to edit messages 🎉

Y'all did it! Congrats to both teams.

https://media.hachyderm.io/media_attachments/files/111/177/051/223/806/093/original/3530ffa089b1fa4a.jpeg 
 hitting ctrl+c (sending SIGINT) at random times is all you need to find an infinite supply of software bugs

https://media.hachyderm.io/media_attachments/files/111/166/338/758/570/808/original/7fa22220305d57e1.jpeg 
 jfc what is discord doing this week, I've seen like 4 different kinds of outages. their status page is all green which is fucking useless, at least they acknowledged the blocking thing: https://discordstatus.com 
 nostr:npub1p4grwm5vzshe7he6jp5gatt0j0707armz7f35mzr3afqmwqr9f9sgaqlwm i'd love to read that artic... 
 @e06c1f25 yeah exactly! I mean that use case is really just "build a current_thread tokio executor from one of your threads and move a channel sender into it, then from the sync side use blocking_recv" (see https://docs.rs/tokio/latest/tokio/sync/mpsc/index.html#communicating-between-sync-and-async-code)

but yeah! 
 nostr:npub1p4grwm5vzshe7he6jp5gatt0j0707armz7f35mzr3afqmwqr9f9sgaqlwm this might be a bad questio... 
 @e06c1f25 it's entirely possible to "avoid async rust as much as possible" if you're not writing primarily networked apps (or other kinds of apps that are asynchronous by nature). I should actually write a guide about that: if you don't really have performance constraints (most don't), it's really easy to pull off. 
 Please stop writing these: https://corrode.dev/blog/async/

This teaches you exactly one thing about async rust (futures must be polled to do work) 90% into the article and the rest is just... conjecture? Mourning async-std? Quoting other poorly researched pieces? 
 Whoa, JetBrains joins the Rust foundation + announces a standalone IDE for Rust

https://blog.jetbrains.com/rust/2023/09/13/introducing-rustrover-a-standalone-rust-ide-by-jetbrains/