News for hackers. Stuff that matters.
Re:Futurelock: A subtle risk in async Rust by toast0 on Saturday November 01, 2025 @01:03AM (#45779382)
It's easier to write all applications, concurrent or not, in a style that works well for concurrency. Lots of applications can benefit from concurrency.

You can do straight line, single threaded, non concurrent code in an actor model. Mostly, that's what most of the actor code will look like. Get a message, update local state in a straight forward way, send a response, repeat.

There are no comments on this comment yet.