Olaf Schlüter
1 min readFeb 17, 2024

Actually it does it pretty well. It does it so well that O'Reilly's "Programming Rust" starts with an example of a program using concurrency in the cursory introduction chapter, something books on many other programming languages are bringing at the end of their journey as an advanced topic, if at all. The whole memory management concept of Rust is for being able to write safe and sound multi-threaded programs - so this is not an afterthought. It is so easy in almost every other language (but FP languages) supporting this feature to get multi-threading wrong, in Rust it is almost impossible. And if you find concurrency easy in GO, the concept is there in Rust. Just use channels for orchestrating threads and you are doing it the GO way. But in Rust you have more options for orchestrating threads, in GO you have only one.

Unless you give more details to why you think Rust does concurrency bad I am assuming you do not know what you are talking about on this particular topic.

Sign up to discover human stories that deepen your understanding of the world.

Free

Distraction-free reading. No ads.

Organize your knowledge with lists and highlights.

Tell your story. Find your audience.

Membership

Read member-only stories

Support writers you read most

Earn money for your writing

Listen to audio narrations

Read offline with the Medium app

Olaf Schlüter
Olaf Schlüter

Written by Olaf Schlüter

IT security specialist, Physicist by education, believing in God as for the exceptional harmony of the laws of nature to create and support life.

Responses (1)

Write a response