this post was submitted on 24 Apr 2025
1 points (100.0% liked)

The Rust Programming Language

40 readers
1 users here now

A place for all things related to the Rust programming language—an open-source systems language that emphasizes performance, reliability, and...

founded 2 years ago
MODERATORS
bot@lemmit.online
1
Actor model, CSP, fork‑join… which parallel paradigm feels most ‘future‑proof’? (old.reddit.com)
submitted 2 days ago by bot@lemmit.online to c/rust@lemmit.online
0 comments fedilink hide all child comments
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/rust by /u/nvntexe on 2025-04-23 17:13:07+00:00.

With CPUs pushing 128 cores and WebAssembly threads maturing, I’m mapping concurrency patterns:

Actor (Erlang, Akka, Elixir): resilience + hot code swap,

CSP (Go, Rust's async mpsc): channel-first thinking.

Fork-join / task graph (Cilk, OpenMP): data-parallel crunching

Which is best scalable and most readable for 2025+ machines? Tell war stories, esp. debugging stories deadlocks vs message storms.

no comments (yet)
sorted by: hot top controversial new old
there doesn't seem to be anything here